Skip to main content
Glama
chrishart0

searchconsole-mcp

by chrishart0

query_search_analytics

Retrieve Google Search Console analytics data to analyze keyword performance, clicks, impressions, CTR, and rankings for SEO optimization.

Instructions

Query Google Search Console search analytics data.

This is the main keyword research tool. Returns rows with clicks,
impressions, CTR, and average position.

Args:
    site_url: The site URL as it appears in Search Console
        (e.g. "https://mychefai.com" or "sc-domain:mychefai.com").
    start_date: Start date in YYYY-MM-DD format.
    end_date: End date in YYYY-MM-DD format.
    dimensions: List of dimensions to group by. Options: query, page,
        date, country, device, searchAppearance. Defaults to ["query"].
    row_limit: Max rows to return (1-25000, default 1000).
    start_row: Starting row offset for pagination (default 0).
    dimension_filters: Optional list of filter objects. Each filter has:
        - dimension: the dimension to filter on (e.g. "query", "page")
        - operator: one of "contains", "equals", "notContains",
          "notEquals", "includingRegex", "excludingRegex"
        - expression: the filter value
        Example: [{"dimension": "query", "operator": "contains",
                    "expression": "keto"}]
    search_type: Type of search results. One of: web, image, video,
        news, discover, googleNews. Default "web".
    aggregation_type: How to aggregate results. One of: auto, byPage,
        byProperty. If omitted, the API auto-selects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes
start_dateYes
end_dateYes
dimensionsNo
row_limitNo
start_rowNo
dimension_filtersNo
search_typeNoweb
aggregation_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes what data is returned (rows with clicks, impressions, CTR, average position) and mentions pagination behavior via start_row. However, it doesn't disclose important behavioral traits like rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though 'Query' implies reading).

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 description is appropriately sized and well-structured with a clear purpose statement followed by detailed parameter documentation. Every sentence earns its place, though the parameter section is quite lengthy (which is necessary given the complexity). It could be slightly more front-loaded with key usage guidance.

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?

Given the tool's complexity (9 parameters, no annotations, but with output schema), the description is quite complete. It thoroughly documents all parameters and their semantics. The presence of an output schema means the description doesn't need to explain return values. However, it could better address behavioral aspects like rate limits or error handling.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. It explains all 9 parameters with examples, default values, valid options (e.g., dimensions options, search_type values), and even includes a complete example for dimension_filters. This adds substantial meaning beyond the bare schema.

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?

The description clearly states the tool's purpose: 'Query Google Search Console search analytics data' with specific verb ('Query') and resource ('search analytics data'). It distinguishes this as 'the main keyword research tool' and specifies the returned metrics (clicks, impressions, CTR, average position), making it distinct from sibling tools like list_sitemaps and list_sites.

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?

The description provides clear context by identifying this as 'the main keyword research tool,' which implicitly suggests when to use it. However, it doesn't explicitly state when to use alternatives like list_sites or list_sitemaps, nor does it provide exclusion criteria or prerequisites for usage.

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/chrishart0/searchconsole-mcp'

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