call-actor fails with content[1] validation error for upwork-vibe/upwork-job-scraper

[inbusco]

Bug: call-actor fails with content[1] validation error for upwork-vibe/upwork-job-scraper

Environment

• Claude Desktop (Cowork mode) on Windows
• Apify MCP connector via Settings → Connectors
• URL: https://mcp.apify.com?tools=actors,docs,storage,apify/rag-web-browser

Actor

upwork-vibe/upwork-job-scraper (upwork-vibe/upwork-job-scraper)

Input

{
  "limit": 5,
  "fromDate": "2026-02-27",
  "toDate": "2026-03-06",
  "includeKeywords.keywords": ["n8n"],
  "includeKeywords.matchTitle": true,
  "includeKeywords.matchDescription": true,
  "client.paymentMethodVerified": true
}

Expected behavior

Actor runs and results are returned to the MCP client.

Actual behavior

The MCP tool call-actor fails with an invalid_union validation error at content[1]. The error indicates the response contains a content type that doesn't match any of the expected types (text, image, audio, resource_link, resource).

The actor never executes on Apify — no runs appear in the Apify dashboard. The error occurs at the MCP protocol level before or during response serialization.

content[0] (text summary) appears to parse fine. content[1] (likely a dataset link or resource reference) fails validation.

Workaround (partial)

• Running the actor manually via Apify Console works fine
• get-dataset-list and get-dataset-items storage tools work correctly to retrieve data from manually-triggered runs
• Only call-actor is affected

Steps to reproduce

1. Add Apify MCP connector in Claude Desktop via Settings → Connectors
2. Open Cowork, call mcp__Apify__call-actor with the actor and input above
3. Observe invalid_union error at content[1]
4. Check Apify dashboard — no new runs created

Notes

• Tested multiple times with different inputs, same error every time
• The actor works fine when called directly via Apify Console or REST API
• This may affect other actors that return similar response formats
• Parameters available on call-actor: actor, step, input, callOptions (memory, timeout) — no async parameter exposed

[jirispilka]

Thank you for reporting. I'll take a look

[inbusco]

Apify connector was working with another actor, issue is created in Apify on the actor's page!

[jirispilka]

Thank you again, just for our reference, here is the issue at console.apify.com: https://console.apify.com/actors/YdYsB7rsRY0EUb1lP/info/issues/JWCeXgaicjh0iCu74?build=latest