invalid_input

invalid_input

Message

One or more request fields are missing or malformed.

HTTP status: 400 Bad Request

How to fix

1. Check the param field in the error body. It names the exact input that failed — tags[2], interval, webhookUrl, etc. The CLI prints this on the line below the message; the MCP tool error payload includes it as a structured field.
2. Consult the API reference for the endpoint you called. Each endpoint's schema documents required fields, allowed types, and enum values.
3. Confirm types. tags must be string[], not a comma-separated string. intervalMinutes must be a number, not "5". Strict JSON parsing rejects coercion.
4. Check enum values. Fields like interval, pageType, mode accept a fixed set documented in the schema. Anything else returns this code with param pointing at the bad field.

What this means

The request body parsed but failed schema validation. This is the catch-all for field-level errors not covered by a more specific code like invalid_url or invalid_workflow.

Related errors

• invalid_url — specifically the url field
• invalid_workflow — workflow DAG validation
• node_type_unknown — workflow node type not recognized

Still stuck?

Contact support with your request_id (looks like req_01HF3JKB...). Include the request body and we'll trace the schema check.