Skip to main content
A tool can be discoverable and still be unavailable for the current request. HyperGSC checks scope, property access, plan, provider readiness, and quota at execution time.

​
Common error codes

A response may use other operation-specific codes. Preserve the returned code, message, limits, and readiness date rather than replacing them with a guessed explanation.

​
Tool results and transport failures

Tool execution errors can be returned as MCP results with isError: true, structured content, and a JSON text representation. Do not assume a successful HTTP transport status means the tool succeeded. Authentication or protocol failures can occur before tool execution and need separate client handling.

​
Check availability before large requests

Call get_capabilities and get_usage before a large analysis or paid-provider batch. Tool discovery includes availability metadata under _meta["com.hypergsc/availability"]. A cached catalog can become stale after quota use, plan changes, server updates, or authorization changes.

​
Keep requests bounded

Inspect no more than ten URLs in a batch. Analytics requests have row limits and source coverage limits. Provider research can consume quota for dispatched failures as well as successful responses. Do not repeatedly retry an invalid request or an exhausted allowance. Reuse an idempotency key when retrying the same SEO-change record, and refresh versioned state before retrying a conflicting deletion. See troubleshooting for user-facing fixes and plans and usage for shared allowances.