mcp-seo-audit

get_search_analytics

Read-onlyIdempotent

Retrieve Google Search Console analytics for a property, grouped by query, page, device, country, or date, to see what drives clicks, impressions, and rankings.

Instructions

Get search analytics data for a specific property.

Args:
    site_url: Exact GSC property URL (e.g. "sc-domain:example.com")
    days: Number of days to look back (default: 28)
    dimensions: Dimensions to group by, comma-separated (query, page, device, country, date, searchAppearance)
    row_limit: Number of rows to return (default: 20, max: 500)
    search_type: Type of search results (WEB, IMAGE, VIDEO, NEWS, DISCOVER)

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": {
      "site_url": "<site_url>"
    },
    "name": "get_search_analytics"
  }
}

Input Schema

Name	Required	Default
`days`	No
`site_url`	Yes
`row_limit`	No
`dimensions`	No	query
`search_type`	No	WEB

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Apr 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds useful operational detail (default lookback of 28 days, row_limit max of 500, valid search_type values), but says nothing about rate limits, quota consumption, or result ordering/pagination.

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 purpose sentence is front-loaded and the Args block is a tight, scannable list with no filler. The Python-docstring formatting is slightly informal but costs nothing in clarity.

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?

An output schema exists, so return values need not be described, and the parameter coverage is thorough. What is missing is differentiation from the many sibling analytics tools and any indication of quotas or result limits beyond row_limit.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so well: it gives an example site_url format ('sc-domain:example.com'), defaults for days and row_limit, a hard cap of 500 rows, the allowed dimension tokens, and the full enum of search_type values that the schema does not encode as an enum.

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?

States a specific verb ('Get') and resource ('search analytics data') scoped to 'a specific property', so the agent knows the operation. However, it does nothing to distinguish itself from close siblings like get_advanced_search_analytics, get_search_analytics_snapshot, or get_performance_overview, leaving the agent to guess which analytics tool to pick.

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 when-to-use guidance, no prerequisites, and no named alternatives despite several overlapping siblings in the same family. The only implicit context is that it requires a GSC property, which is inferable from the required site_url parameter.

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

Deploy Server