Skip to main content
Glama
conorbronsdon

Google Search Console (GSC) MCP

Query search performance

gsc_search_analytics
Read-onlyIdempotent

Fetch clicks, impressions, CTR, and position from Google Search Console for any property and date range, grouped by query, page, country, device, or date. Use it to find top queries/pages or track trends.

Instructions

Query Search Console search analytics for a property over a date range: clicks, impressions, CTR, and average position, grouped by the dimensions you pass (query, page, country, device, date). Returns compact rows. Use this for 'what are my top queries / pages' and trend questions. GSC data lags ~2-3 days, so end your range a few days before today.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSearch type filter. Defaults to web when omitted.
end_dateYesEnd date, YYYY-MM-DD (Pacific Time, inclusive).
site_urlYesThe Search Console property. Use the exact form shown by gsc_list_sites: a Domain property is 'sc-domain:example.com'; a URL-prefix property is the full origin with a trailing slash, e.g. 'https://example.com/'.
row_limitNoMax rows to return (default 25, cap 1000). Keep low; rows cost tokens.
dimensionsNoHow to group rows. Default ['query']. Combine for breakdowns, e.g. ['page','query'].
start_dateYesStart date, YYYY-MM-DD (Pacific Time, inclusive).
dimension_filter_groupsNoOptional filters, e.g. only rows where page contains '/blog/'. Each group's filters are AND-ed.
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and destructiveHint. The description adds valuable non-obvious behavior: GSC data lags ~2-3 days and results are compact rows, which informs end-date selection and token expectations.

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: the first states the function and outputs, the second provides usage guidance and a caveat. No filler or repetition of schema content.

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?

Covers purpose, metrics, dimensions, date-range behavior, and data freshness in just two sentences. Combined with rich schema and annotations, this is fully sufficient for an agent to select and invoke the tool correctly.

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% with detailed parameter docs (site_url examples, row_limit cap, dimensions enum, filter groups). The description's mention of dimensions and date range adds no new semantic information beyond what the schema already provides.

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?

Specific verb+resource: 'Query Search Console search analytics' with explicit metrics (clicks, impressions, CTR, average position) and dimensions. This clearly distinguishes it from siblings like gsc_list_sites and gsc_submit_sitemap.

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

Usage Guidelines4/5

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

States explicit use cases ('what are my top queries / pages' and trend questions) and provides a temporal caution about data lag. No explicit exclusions or alternatives, but the sibling tools are quite different.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conorbronsdon/gsc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server