invalid_request
Common cases:
- Required query parameter omitted (e.g.
GET /v1/noteswithoutprojectId). - Enum field given an unknown value (e.g.
?status=BOGUSagainst/v1/posts). - Date filter with the wrong format (
?dateFrom=15/05/2026— must beYYYY-MM-DD). - A request body fails validation on a write endpoint.
details field, when present, names the offending
parameter:
invalid_request is rejected before any
write would have happened.
On the MCP surface, invalid_request also covers confirmation-token
failures on the two-phase tools: details.reason is
confirmation_invalid (the subject changed since the proposal, or the
token belongs to a different action) or confirmation_expired (past the
~5-minute TTL). Recover by calling the tool again without a token to get
a fresh proposal — see
MCP tools § Two-phase confirmation.