GSC SEO MCP

by samalyxx

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

quick_wins

Identify keywords ranking 4-15 where better content, internal links, or snippets can win traffic.

Instructions

Find keywords ranking around positions 4-15 where better content, internal links, or snippets can win traffic.

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": "quick_wins"
  }
}

Input Schema

Name	Required	Description
`siteUrl`	No	Google Search Console property URL, e.g. sc-domain:example.com or https://www.example.com/.
`startDate`	No	Start date in YYYY-MM-DD. If omitted, days is used.
`endDate`	No	End date in YYYY-MM-DD. If omitted, days is used.
`days`	No	Lookback window when startDate/endDate are omitted.
`minImpressions`	No
`minPosition`	No
`maxPosition`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not state whether the tool is read-only, modifies data, or requires specific permissions. The method for determining 'opportunities' is opaque.

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

Conciseness5/5

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

The description is a single sentence that is concise, front-loaded, and contains no unnecessary words. It effectively communicates the core functionality.

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?

Given the tool has 8 parameters and no output schema, the description is insufficient. It does not explain the output format, response structure, pagination, or how results are ordered. The agent lacks essential context for invocation.

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 50%, and the description adds no additional meaning beyond what the schema already provides for parameters. It mentions the ranking range (4-15) which aligns with defaults, but no further parameter semantics.

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

Purpose5/5

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

The description clearly identifies the tool's function: finding keywords in rank positions 4-15 with opportunities for traffic wins via content, links, or snippets. It distinguishes from siblings like 'content_decay' or 'internal_link_opportunities' by focusing specifically on positions 4-15.

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 description implies usage for identifying quick wins but does not provide explicit guidance on when to use this tool versus alternatives like 'ctr_opportunities' or 'internal_link_opportunities'. No exclusion criteria or context for when not to use.

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