Errors and recovery
Loading server catalog…. Download catalog
Advarde MCPAvailable subject to your connection’s permissions.
Description: Distinguish HTTP errors, JSON-RPC errors, tool failures, and incomplete jobs.
Documentation: Getting started
Output: See the protocol description and workflow notes below.
Access: Workspace-scoped MCP authentication.
HTTP and protocol errors
401 means authentication failed. Access checks may produce 403. Invalid JSON-RPC requests may return a top-level error. Do not interpret HTTP 200 alone as a successful tool operation.
Tool errors
Inspect result.isError and result.structuredContent. Tool failures contain an error code and status, with a human-readable message in content. Success data is returned as structuredContent and JSON text in content; environment identifies the configured Ads mode.
Job recovery
Submitted or processing jobs are not completed changes. Inspect every operation result. Retrieve the existing change before retrying an uncertain write. Use ads_retry_bulk_submission only for eligible uncertain bulk submissions after explicit authorization; other uncertain writes require reconciliation.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.