Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

get_striking_distance_keywords

Identify Google Search Console keywords ranking positions 4–15 to prioritize page-2-to-top-3 growth opportunities, with each row showing its ranking page and gap to page 1.

Instructions

Queries ranking ~4-15 (page-2-to-top-3) — the most actionable growth band.

Each row reports the ranking page and the gap to page 1 (position - 3).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
siteNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/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 burden. It never says the tool is a read-only query with no mutations, does not mention the default 28-day window or how `limit` caps results, and does not state whether results are site-scoped or account-wide. The one behavioral detail it gives, the row shape and 'position - 3' gap formula, overlaps what the output schema already documents.

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?

Two short sentences with the ranking band and the actionable framing front-loaded; no filler. The second sentence is redundant with the output schema, which is the only waste.

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

Completeness3/5

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

The output schema covers return values and the description covers the ranking band, so the core is present. However, with three undocumented parameters and no annotations, an agent still cannot tell what `site: null` or `days` actually change about the result set.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters (days, site, limit), each with only a type and default. The description adds no meaning to any of them — nothing on what `days` measures, what happens when `site` is null, or how `limit` interacts with ranking order. At 0% coverage the description was expected to compensate and does not.

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 definition names a specific resource (keywords ranking in the striking-distance band) and defines that band precisely as positions ~4-15, which is far more specific than the bare tool name. It does not explicitly distinguish itself from siblings like get_top_opportunities, so it stops short of a 5.

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?

'The most actionable growth band' implies the use case (find keywords worth pushing to page 1) but never states when to choose this over get_top_opportunities or get_page_performance. Usage is inferable rather than instructed, which is the definition of a 3.

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