Skip to main content
Glama
modelbrain-search-console

modelbrain-search-console

Official

Search performance report

search_performance
Read-onlyIdempotent

Retrieve Google Search Console clicks, impressions, CTR, and average position grouped by query, page, country, device, date, or search appearance; filter by date ranges up to 16 months.

Instructions

Clicks, impressions, CTR and average position from Google Search, grouped by any of query, page, country, device, date or searchAppearance, with optional filters. Covers up to 16 months. Defaults to the last 28 days of final data (ending 3 days ago) and 100 rows.

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": {
      "site_url": "<site_url>"
    },
    "name": "search_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoAll filters must match.
end_dateNoLast day, YYYY-MM-DD. Default: 3 days ago.
site_urlYesThe Search Console property, for example sc-domain:example.com or https://example.com/. A plain domain or page URL also works: it is matched to the right property.
row_limitNoDefault: 100
start_rowNoFor paging. Default: 0
dimensionsNoHow to group rows. Empty gives one row of totals.
start_dateNoFirst day, YYYY-MM-DD. Default: 28 days before end_date.
search_typeNoDefault: web

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the burden is lower. The description still adds meaningful traits the annotations do not carry: a 16-month data retention ceiling and a three-day final-data lag that affects any date window the agent computes. It does not mention quota or rate-limit behavior, which is the main remaining gap.

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 dense sentences, front-loaded with what is returned before moving to grouping and defaults. Every clause carries information; there is no filler or repetition of the title.

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?

With eight parameters, full schema coverage and rich annotations, the description supplies everything an agent needs to call the tool correctly: metrics, grouping options, filter capability, time bounds and defaults. No output schema exists, but the metric list effectively characterizes the result shape.

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 coverage is 100%, so every parameter is already documented, including defaults for dates, row_limit and search_type. The description only echoes the grouping-dimension semantics and defaults that the schema already states, adding little new meaning, so the baseline of 3 applies.

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 names the exact metrics returned (clicks, impressions, CTR, average position), the source (Google Search), and the allowed grouping dimensions. It is highly specific about the resource, though it omits an explicit verb and does not name a sibling alternative; the distinction from compare_periods or list_sitemaps is left to inference.

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?

It gives concrete operational context: coverage of up to 16 months, a default window of the last 28 days of final data, and a default of 100 rows. It does not state when to prefer this over compare_periods for period-over-period questions, so the guidance is clear but not exclusionary.

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