Skip to main content
Glama
Sign In
flin-google-search-console-mcp

flin-google-search-console-mcp

by flin-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_dimension_breakdown

Read-onlyIdempotent

Break down Google Search Console Search Analytics by a single dimension for a date range, so you can compare query, page, country, or device performance.

Instructions

Get a single-dimension Search Analytics breakdown.

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>",
      "dimension": "<dimension>"
    },
    "name": "get_dimension_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
filtersNo
end_dateYes
site_urlNo
dimensionYes
row_limitNo
start_rowNo
data_stateNo
start_dateYes
search_typeNoweb

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no word on quota/rate limits, pagination behavior, which dimension values are valid, or how filters constrain results, all of which matter for a Search Console analytics call.

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

Conciseness3/5

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

It is a single front-loaded sentence with no padding, so nothing needs trimming. However, brevity here comes at the cost of saying almost nothing beyond the name, so it is concise without being informative.

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?

An output schema exists, so return values need not be explained, but for a 10-parameter reporting tool the description is far too thin. The valid dimension values, filter format, date conventions, and pagination defaults are all left to inference.

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?

With 10 parameters and 0% schema description coverage, the description must carry the burden, but it only vaguely gestures at the 'dimension' parameter. start_date/end_date formats, the filters array structure, row_limit/start_row pagination semantics, search_type defaults, and data_state are all undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence largely restates the tool name: 'get_dimension_breakdown' becomes 'Get a single-dimension ... breakdown.' The only added information is the domain ('Search Analytics'), which does not distinguish it from siblings like query_performance, get_top_queries, or get_top_pages, whose names suggest overlapping reporting behavior.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus query_performance, get_top_queries, or get_top_pages, nor any mention of prerequisites or exclusions. An agent must guess which reporting tool to select.

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

Deploy Server

Other Tools