Skip to main content
A v3 tool can return a successful MCP transport response with isError: true. Always inspect the tool result, then use structuredContent.code and the associated fields rather than parsing rendered prose. Common recovery patterns include:
  • correct a validation field and call again;
  • call get_status after a wrong-account response;
  • re-read a versioned noun after a revision conflict;
  • preserve per-seller or per-source outcomes from a partial result; and
  • re-read after partialWrite: true before deciding whether to retry.
NOT_FOUND can intentionally hide whether an object exists outside the active account. Do not treat it as evidence about another account.

Full error reference

Review the canonical error envelope, status mapping, retry behavior, and troubleshooting guidance shared with stable v2.