Skip to main content
Glama
Agency MCP Server

Agency MCP Server

Search Console report

search_console_report
Read-only

Retrieve read-only Search Console analytics—clicks, impressions, CTR, and average position—for a client property; returns clearly marked fixture data when credentials are unavailable.

Instructions

Read-only Search Console search analytics (clicks, impressions, CTR, average position) for the client's property. Without credentials it returns sample rows marked as fixture data.

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": {
      "client": "<client>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "search_console_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient id from the server's config (dental, cafe, plumber).
endDateYes
rowLimitNo
startDateYes
dimensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: it discloses that missing credentials cause the tool to return sample rows explicitly marked as fixture data, which prevents an agent from treating fabricated numbers as real results.

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 sentences, zero filler, with the resource and metrics front-loaded and the fixture caveat trailing as a qualification. Every clause carries information the agent needs.

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

Completeness3/5

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

The description adequately covers what the tool is and its return metrics, which matters since no output schema exists. However, for a five-parameter tool with three required fields and 20% schema coverage, the omission of any parameter guidance (date format expectations, dimension combination rules, rowLimit behavior) leaves notable gaps before invocation.

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 only 20% — just the 'client' field — and the description contributes nothing about startDate, endDate, rowLimit, or the dimensions array (including its three-item cap and allowed values). With four of five parameters undocumented across both schema and description, an agent cannot determine valid date semantics or dimension behavior without guessing.

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 a specific verb+resource (Search Console search analytics) and enumerates the returned metrics (clicks, impressions, CTR, average position), so the agent knows exactly what data it yields. It does not explicitly contrast itself with siblings like answer_engine_visibility or core_web_vitals, but the domain is distinct enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must infer that this is the tool for organic search performance data. There is no explicit statement of when to prefer it over other visibility tools, and no prerequisites or exclusions. The fixture-data caveat is the only conditional guidance offered.

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