Skip to main content
Glama
ahonn

Google Search Console MCP Server

by ahonn

enhanced_search_analytics

Analyze Google Search Console data with advanced filtering, regex matching, and quick wins detection to identify optimization opportunities.

Instructions

Enhanced search analytics with up to 25,000 rows, regex filters, and quick wins detection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteUrlYesThe site URL as defined in Search Console. Example: sc-domain:example.com (for domain resources) or http://www.example.com/ (for site prefix resources)
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format
dimensionsNoComma-separated list of dimensions to break down results by, such as query, page, country, device, searchAppearance
typeNoType of search to filter by, such as web, image, video, news
aggregationTypeNoType of aggregation, such as auto, byNewsShowcasePanel, byProperty, byPage
rowLimitNoMaximum number of rows to return (up to 25,000 for enhanced performance)
pageFilterNoFilter by a specific page URL. Use with filterOperator.
queryFilterNoFilter by a specific query string. Use with filterOperator.
countryFilterNoFilter by a country using ISO 3166-1 alpha-3 code (e.g., USA, CHN).
deviceFilterNoFilter by device type.
filterOperatorNoOperator for page and query filters. Defaults to "equals". Enhanced with regex support.equals
regexFilterNoAdvanced regex filter for intelligent query matching
enableQuickWinsNoEnable automatic quick wins detection
quickWinsThresholdsNoCustom thresholds for quick wins detection
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'enhanced performance' and 'quick wins detection' but doesn't clarify what 'enhanced' means operationally, whether this is a read-only or mutating operation, potential rate limits, or what 'quick wins' entails in practice. The description lacks critical behavioral context for a complex tool.

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?

The description is extremely concise—a single sentence that efficiently lists key features without redundancy. It's front-loaded with the core purpose and doesn't waste words, making it easy for an agent to parse quickly.

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

Completeness2/5

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

For a complex tool with 15 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how 'quick wins' are presented, or the operational implications of 'enhanced' features. The agent lacks sufficient context to understand the tool's full behavior and output.

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 parameters are well-documented in the schema itself. The description adds marginal value by hinting at 'regex filters' and 'quick wins detection' which correspond to specific parameters, but doesn't provide additional semantic context beyond what's already in the schema descriptions. Baseline 3 is appropriate given high schema coverage.

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 clearly states the tool performs 'enhanced search analytics' with specific capabilities (up to 25,000 rows, regex filters, quick wins detection). It distinguishes from the simpler 'search_analytics' sibling by highlighting enhanced features, though it doesn't explicitly contrast with 'detect_quick_wins' which might overlap in functionality.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_analytics' or 'detect_quick_wins'. The description mentions capabilities but doesn't specify use cases, prerequisites, or exclusions that would help an agent choose appropriately among siblings.

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/ahonn/mcp-server-gsc'

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