Skip to main content
Glama

search_analytics

Query Google Search Console search analytics to retrieve clicks, impressions, CTR, and average position for a site, with filters by query, page, country, device, and date range.

Instructions

Query search analytics data from Google Search Console. Returns clicks, impressions, CTR, and position for your site.

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

Input Schema

NameRequiredDescriptionDefault
endDateYesEnd date in YYYY-MM-DD format
siteUrlYesSite URL exactly as it appears in Search Console (e.g. https://example.com/ or sc-domain:example.com)
rowLimitNoMax rows to return (default 100, max 25000)
startDateYesStart date in YYYY-MM-DD format
dimensionsNoComma-separated dimensions: query, page, country, device, searchAppearance, date
pageFilterNoFilter by page URL. Prefix with regex: for regex matching.
searchTypeNoType of search results to queryweb
queryFilterNoFilter by search query. Prefix with regex: for regex matching.
deviceFilterNoFilter by device type
countryFilterNoFilter by country (ISO 3166-1 alpha-3, e.g. USA, GBR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0-fork.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose the return metrics (clicks, impressions, CTR, position), which is the only source for that information since there is no output schema. It omits important behavior: Search Console data lag, the ~16-month retention window, quota/rate limits, and the row-limit cap.

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?

Two short sentences, front-loaded with the source system and followed by the returned metrics. Nothing is redundant, though it is too thin rather than too verbose.

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

Completeness3/5

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

For a 10-parameter query tool with no annotations and no output schema, the description covers the resource and returns but not the operational caveats an agent would want (data freshness, quotas, row limit consequences). Parameter documentation is fully covered by the schema, which keeps this at minimum viable rather than deficient.

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 100%, so every parameter, including filters, dimensions, and searchType enums, is already documented with formats and constraints. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 analytics data from Google Search Console') and names the returned metrics. It is unambiguous against siblings like list_sites and inspect_url, though it never explicitly differentiates itself from them.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites such as needing Search Console access or a verified site. The agent must infer usage entirely from the name and schema.

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

Deploy Server

Other Tools