Google Search Console MCP

Overview Schema Source Related Servers Discussions Admin

Find working keywords

gsc_top_queries

Retrieve top search queries from Google Search Console for one or multiple properties, with filters for query, page, country, and device, to analyze SEO performance.

Instructions

Fetch top query rows for one property, selected properties, or all properties. Supports filters for query, page, country, and device.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "gsc_top_queries"
  }
}

Input Schema

Name	Required	Default
`type`	No	web
`limit`	No
`device`	No
`country`	No
`endDate`	Yes
`siteUrl`	No
`allSites`	No
`siteUrls`	No
`dataState`	No	final
`startDate`	Yes
`includePages`	No
`pageContains`	No
`queryContains`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Fetch' implies a read operation, but the description does not disclose dataState behavior, pagination, return format, authentication needs, or effects of options like allSites.

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?

The description is a single front-loaded sentence with no filler. It is appropriately concise, though the extreme brevity leaves out important operational detail for a tool with 13 parameters.

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's 13 parameters, absence of annotations, and lack of an output schema, the description is too sparse. It provides a useful high-level summary but omits significant behavioral and parameter details needed for correct invocation in varied scenarios.

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 0%, so the description must add meaning. It maps the query, page, country, and device filters to the relevant parameters and hints at site selection via one/selected/all properties. However, many parameters such as type, limit, dataState, and includePages remain unexplained.

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 states a specific verb and resource: 'Fetch top query rows', and clarifies the scope as one, selected, or all properties. It is clear about the core action, though it does not explicitly distinguish itself from similar siblings like gsc_search_analytics or gsc_keyword_opportunities.

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?

The description provides no guidance on when to use this tool versus alternatives such as gsc_search_analytics or gsc_keyword_opportunities. It implies usage for top queries but lacks explicit context, conditions, or exclusions.

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

Deploy Server