Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

search_console_search_analytics

Query Google Search performance metrics for a Search Console property to analyze clicks, impressions, CTR, and rankings by date, query, page, country, or device.

Instructions

Query Google Search performance metrics for a Search Console property.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "search_console_search_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesInclusive YYYY-MM-DD end date.
site_urlNoSearch Console property, for example sc-domain:example.com. Use list_sites to find one.
row_limitNo
start_rowNo
data_stateNo
dimensionsNo
start_dateYesInclusive YYYY-MM-DD start date.
search_typeNo
aggregation_typeNo
dimension_filter_groupsNoOptional Search Console filter groups using API fields groupType and filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/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, and it discloses almost nothing: it never states this is a read-only query, says nothing about API quota/rate limits (relevant for the Search Console API), row limits or pagination behavior, or data freshness. The only implicitly useful detail is that results are scoped to a property.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is not wasteful at the sentence level, though it reflects under-specification rather than discipline.

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

Completeness1/5

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

For a 10-parameter reporting tool with no annotations and no output schema, one sentence is far too thin. It does not describe the returned row structure (dimensions plus clicks/impressions/CTR/position), pagination via row_limit/start_row, or how data_state affects results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 40%, so the description was expected to compensate and adds zero parameter meaning. Three enum parameters (dimensions, search_type, data_state, aggregation_type) are self-explanatory from their values, but row_limit/start_row paging, dimension_filter_groups shape, and the absence of any metric-selection parameter are all left unexplained.

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 performance metrics' tied to 'a Search Console property'. This clearly separates it from sibling tools like search_console_inspect_url or search_console_list_sites, though the description itself never names an alternative.

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 when-to-use or when-not-to-use guidance, no prerequisites (e.g., that a property must be verified and selected), and no routing to sibling tools. The alternative reference ('Use list_sites to find one') exists only inside the input schema, not the description.

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