QuerySail: Google Search Console

Get Search Console performance

get_performance

Read-onlyIdempotent

Use this to retrieve Google Search Console search performance (clicks, impressions, CTR, average position) for one property. With no dimensions it returns property totals. Add dimensions to break results down by date, hour, query, page, country, device or searchAppearance, and filters to narrow to specific queries, pages, countries, devices or search appearances (for example mobile traffic to pages containing '/blog/'). search_type selects web (default), image, video, news, discover or googleNews results; discover and googleNews have no queries. For what happened in the last hours or days, group by hour (data_state 'hourly', last 10 days only, preliminary). Dates are Pacific Time. If no dates are given it uses the last 28 finalized days (or yesterday and today for hourly) and reports the exact dates it used. Covers one period at a time. Rows are bounded (default 20, max 100); page through with the returned cursor. Google returns only top rows for query/page breakdowns, so results are not guaranteed to be complete, and a missing row does not mean zero. Figures are observed values and do not identify causes. Read-only; cannot request indexing or change anything in Search Console.

Input Schema

Name	Required	Description
`cursor`	No	Opaque cursor from coverage.nextCursor of the previous call with the same arguments.
`filters`	No	All filters are combined with AND.
`end_date`	No	Inclusive end date, YYYY-MM-DD (Pacific Time). Provide together with start_date.
`row_limit`	No	Rows per call. Default 20, maximum 100.
`data_state`	No	'final' (default) returns finalized data only; 'all' includes recent preliminary data; 'hourly' is required (and implied) when grouping by hour.
`dimensions`	No	Group results by these dimensions. Omit for a single totals row. 'hour' cannot be combined with 'date' and needs a range within the last 10 days. 'searchAppearance' lists search features such as review snippets or video and must be the only dimension; to break one feature down further, filter by searchAppearance instead.
`start_date`	No	Inclusive start date, YYYY-MM-DD (Pacific Time). Provide together with end_date.
`property_id`	Yes	Exact property ID from list_properties, e.g. 'sc-domain:example.com' or 'https://example.com/'.
`search_type`	No	Which results to report. Default 'web' (the combined 'All' tab). 'news' is the News tab in Search; 'googleNews' is news.google.com and the Google News app.
`connection_id`	No	Optional: force a specific Google connection when the property is visible to several.
`include_totals`	No	When grouping by dimensions, also fetch a separate property-level totals row. Default false.

Output Schema

Name	Required	Description	Default
`rows`	No
`units`	No
`totals`	No
`request`	No
`coverage`	No
`property`	No
`freshness`	No
`requestId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds substantial context on top: Pacific Time semantics, the exact default date window, cursor-based paging with row bounds, the critical caveat that query/page breakdowns are truncated to top rows so a missing row does not mean zero, and that figures are observed values not causes.

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?

Front-loaded with the core purpose and dense with useful constraints, with no filler sentences. It is long, but nearly every clause encodes a distinct behavioral rule; a small amount of tightening would be possible.

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

Completeness5/5

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

For an 11-parameter tool with an output schema, the description covers everything an agent needs to invoke it correctly: defaults, time zone, pagination, dimension/filter interactions, search-type semantics, and data-completeness caveats. Return-value structure is left to the output schema, which is appropriate.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already carries per-parameter detail and the baseline is 3. The description still adds meaning beyond it, notably the interaction rules (hour cannot combine with date, searchAppearance must be the only dimension, discover/googleNews have no queries) and a concrete filter example.

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?

Names a specific verb and resource ('retrieve Google Search Console search performance') and enumerates exactly what the metrics are (clicks, impressions, CTR, average position). It is immediately distinguishable from the sibling compare_performance by its stated single-property, single-period scope ('Covers one period at a time').

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

Usage Guidelines5/5

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

Gives explicit conditions for every major mode: omit dimensions for totals, add dimensions to break down, use filters to narrow, group by hour for last-hours/days analysis, and pick search_type per result surface. It also states the default window when no dates are supplied and warns that hourly is limited to the last 10 days.

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

All QuerySail: Google Search Console tools Inspect

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.