Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Disconnect search console

disconnect_search_console
DestructiveIdempotent

Remove the local Google credential and stop collection. Keep the last good sample. The last good sample stays available. An in-flight callback or collection cannot reconnect the site. Returns: { available, connected, property, last_attempt_at, last_success_at, next_run_at, error, stale, snapshot{property,period,checked_at,queries,pages,coverage}, opportunities[{query,clicks,impressions,ctr,position}], terms[{query,last_alert_at,analysis,series}] } Example: await fetch("$ORIGIN/api/sites/SITE_ID/search-console", {method:"DELETE", headers:{"X-CSRF-Token":csrf}}).then(r => r.json()); Errors: 401: account_required or session_ended; 403: account_required or invalid_csrf; 404: site_not_found; 503: sites_unavailable

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "disconnect_search_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSite ID from list_sites or add_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance beyond them: only the LOCAL credential is removed, the last good sample survives, and an in-flight callback or collection cannot silently reconnect the site. It also discloses the CSRF requirement (X-CSRF-Token in the example) and the 401/403/404/503 failure taxonomy, which is meaningful for a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded in sentence one, but 'Keep the last good sample' and 'The last good sample stays available' say the same thing twice, and the Returns blob plus a full fetch code snippet bloat the definition. Trimming the duplication and the example would sharpen it without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so documenting the returned fields (available, connected, property, snapshot, opportunities, terms, etc.) is genuinely necessary and it is present. Errors are enumerated and a call example is given; only auth/credential-revocation scope at the provider side is left slightly ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter already carries 'Site ID from list_sites or add_site.' The description adds no further meaning about the id parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Remove the local Google credential and stop collection.' The retention clause ('Keep the last good sample') distinguishes it from a purge/delete-everything operation, and the sibling list contains connect_search_console/sync_search_console that this clearly reverses. It stops short of naming the counterpart tool, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer 'call this when you want to stop Search Console collection but retain history.' There is no explicit when-to-use/when-not-to-use statement and no named alternative (e.g., 'to reconnect, use connect_search_console'), so an agent must reason from the effect rather than guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pageaudit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources