Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

analyze_gsc_ai_overviews

Analyze Google Search Console queries to estimate AI Overview trigger probability and flag zero-click answer displacement risks for a domain.

Instructions

Analyze Google Search Console queries to identify Google AI Overview (AIO) trigger probability and prevent zero-click answer displacement.

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": {
      "domain": "<domain>"
    },
    "name": "analyze_gsc_ai_overviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to audit (e.g., 'example.com')
query_sampleNoOptional sample of query performance rows from GSC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Analyze' implies a read-only operation, but the description never confirms that, nor does it mention required permissions, whether query_sample is needed for meaningful results, or what the analysis returns.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though the dense jargon ('zero-click answer displacement') could be tightened for clarity.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should explain the shape of the result (probability scores, affected queries, recommendations) and the role of the optional sample. Neither is covered, leaving the agent unable to predict the response.

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%, so both parameters (domain, query_sample) are already documented in the schema. The description adds no extra meaning about how the sample is used or what happens when it is omitted, so the baseline of 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?

The description names a specific verb ('Analyze') and resource ('Google Search Console queries') and states the analytical goal (AIO trigger probability, zero-click displacement). It is clear what the tool does, but it does not differentiate itself from plausible siblings such as geo_audit_domain or get_ai_search_visibility.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over the many adjacent GEO/AI-visibility siblings, nor any stated prerequisites such as GSC connectivity or data availability. The agent must infer the selection context entirely.

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