Skip to main content
Each interface reports failure in its own shape, with the same HTTP status meanings underneath.

MCP tools

A failed tool call returns a normal MCP result with isError: true. Its one text block says what failed, the status behind it, what to do next, and a reference id:
Quote the Reference id when you ask Rippit about a failure. It identifies the exact request. Arguments that don’t match a tool’s schema are rejected before the tool runs, with text that starts Input validation error and describes each problem.

When a retry is safe

Reads and any call that returned 429 are safe to retry. A write that timed out or returned 5xx may have taken effect, so check before repeating it. Idempotency and retries lists which operations are safe to repeat and how to check.

Connection errors

Before any tool runs, the server checks the request’s sign-in. These failures are plain HTTP responses with a JSON body and an x-request-id header:

Bulk API

Errors return a JSON body with a detail field. For most statuses it is a message:
For 422 it is a list with one entry per invalid field, where loc is the path to the field:

Job errors

A request can succeed while the job it started does not. Read the job until status is done or failed:
  • A failed job has the reason in error.
  • A done job can still have skipped rows. Each one is in result.rejected with its 0-based row number and the reason, and every other row was written.
Fix the rejected rows and upload them again. See Idempotency and retries for when re-sending a record updates it, and the Conversations guide and the Tables guide.

Rippit CLI

A failed command exits with status 2 when the command line itself was rejected, and 1 for every other failure. With --format json, stderr holds one object:
When retryable is false, check the result before running the command again. See Rippit CLI for the codes each command returns.