Skip to main content
Glama
Sign In

GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP

by com.gscpap
OverviewDiscussionsAdmin

Search Analytics query

search_analytics_query
Read-only

Query Search Console analytics for a property.

Read-through cache pattern: if the requested date range is fully in the "stable past" (>3 days old) AND the Personal Archive has complete day coverage for it AND search_type=web AND data_state=final, the response is served from the archive (fast, zero GSC quota). Otherwise falls through to the Google API. The response includes a _source field so callers can tell which path was used.

Anonymized queries: archived rows are query-level, and Google leaves anonymized queries out of those, so the archive only answers what it can answer exactly: requests with the "query" dimension or a query filter, and totals (no dimensions, or only "date", no filters) from archived Search Console daily totals. A page, country or device breakdown without query goes to Google while the range is inside Google's ~16-month window. For older ranges the archive answers and adds a note saying the figures exclude anonymized traffic and are lower than Search Console's.

Input Schema

NameRequiredDescriptionDefault
end_dateNoISO date (YYYY-MM-DD). Defaults to 3 days ago (GSC ~3-day lag).
site_urlYesProperty URL exactly as returned by list_sites.
row_limitNoMax rows. Capped at 25000. Default 100.
start_rowNoPagination offset.
data_stateNo"all" includes fresh data and forces Google. "final" allows archive read.all
dimensionsNoAny of "query", "page", "country", "device", "date", "searchAppearance". Omitted means ["query"]; an explicit empty list [] means the property-wide total. NB: searchAppearance forces Google fetch (not in archive schema).
start_dateNoISO date (YYYY-MM-DD). Defaults to 28 days ago.
search_typeNoDefault "web". Non-web types always go to Google.web
dimension_filter_groupsNoRaw GSC filter groups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

It adds substantial behavior beyond the annotations: the read-through cache path, zero-GSC-quota archive reads, the `_source` response field, anonymized-query limitations, and the `note` added for older ranges. These details are exactly the kind of operational context an agent needs for this read-only but open-world query tool.

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 front-loaded with purpose and cache behavior, and the anonymized-query caveat is relevant rather than filler. It is somewhat long, but the length is justified by the complexity of the archive-versus-Google routing behavior.

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

Completeness4/5

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

For a 9-parameter read-only query tool with no output schema, the description covers the key return hints (`_source`, `note`) and the main caveats around anonymized traffic and archive coverage. It does not describe every response field, but it is complete enough to call the tool correctly.

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 baseline is 3. The description adds meaningful semantics for parameters like data_state=final, search_type=web, and dimensions/query filters by linking them to archive eligibility and Google fallback behavior.

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: 'Query Search Console analytics for a property.' It also explains the archive-versus-Google fetch behavior, but it does not explicitly name or differentiate itself from sibling tools such as search_analytics_archive.

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 explains conditions that determine whether the request is served from the archive or Google, including date range, search_type, data_state, and dimensions. However, it gives no explicit when-to-use guidance versus sibling tools like search_analytics_archive or get_search_by_page_query.

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

All GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP toolsInspect
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.

Resources