Skip to main content
Glama
mcp-google-gsc

mcp-google-gsc

by mharnett

gsc_search_analytics

Query Google Search Console search analytics to retrieve clicks, impressions, CTR, and position by query, page, device, country, or date.

Instructions

Query Google Search Console search analytics data. Returns clicks, impressions, CTR, and position for queries, pages, devices, countries, or dates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsc_search_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoEnd date (YYYY-MM-DD or relative like "today")
site_urlNoSite URL (optional - auto-detected from working directory config)
row_limitNoMax rows to return (default 100, max 25000)
dimensionsNoComma-separated dimensions: query, page, device, country, date
start_dateNoStart date (YYYY-MM-DD or relative like "90daysAgo", "30daysAgo", "7daysAgo", "today")
search_typeNoSearch type: web, image, video, news (default "web")
aggregation_typeNoAggregation: auto, byPage, byProperty (default "auto")
dimension_filterNoOptional filter (e.g., "query contains nonprofit", "page contains /blog/", "country equals USA")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the returned metrics but says nothing about permissions/authentication, Search Console's multi-day data lag, sampling, row-cap behavior, or that the operation is strictly read-only — all of which materially affect how an agent should call and interpret it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and followed by the concrete return fields. Every clause carries information; nothing is padding or restatement of the tool name.

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?

With eight parameters, all optional and fully documented in the schema, the definition covers what the tool is and returns, which partly substitutes for the missing output schema. However, for a data-retrieval tool with no annotations it omits freshness/latency expectations and any hint about defaults such as site auto-detection consequences, leaving the agent to guess at operational behavior.

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 date formats, dimension list, filters, and search_type is already documented. The description adds no meaning beyond the schema (e.g., how dimensions interact with aggregation_type or how filters compose), so the baseline of 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?

States a specific verb and resource ('Query Google Search Console search analytics data') plus the exact metrics returned, which is enough to distinguish it from siblings like gsc_inspection and gsc_list_sites without opening the schema. It stops short of explicitly naming those siblings as alternatives.

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 explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools for inspection, site listing, or client context. The reader must infer from the metric list that this is the performance-reporting tool rather than the diagnostic or configuration one.

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