Skip to main content
Glama

Search Console evidence

search_console_evidence
Read-onlyIdempotent

Search Console evidence for one website: action, gates, and landing-page rows. Same from/to/time_zone/currency as analytics_snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_console_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoinclusive end YYYY-MM-DD; default today
fromNoinclusive start YYYY-MM-DD; default last 60 days
periodNonamed window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month
currencyNolowercase ISO 4217 code
time_zoneNoIANA time zone; default UTC
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website
granularityNoday, week, or month; default day

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds that it returns evidence for one website with specific row types, but does not disclose auth needs, rate limits, data freshness, or other limitations beyond the schema and output schema. With annotations carrying the behavioral load, a 3 is appropriate.

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?

Two sentences, front-loaded with the tool's purpose and followed by a terse parameter cross-reference. It is efficient with no filler, though 'action, gates' is jargon that could be clarified without significant bloat.

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 a fully described 7-parameter schema and an output schema, the description need not explain return fields or parameter formats. It states the subject and scope well enough for invocation, but omits selection guidance versus analytics_snapshot and leaves 'action' and 'gates' unexplained. Those gaps keep it from a 5.

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 description coverage is 100%, so all seven parameters, including from/to/period/website_id/granularity, are documented in the schema. The description adds only that from/to/time_zone/currency follow analytics_snapshot's conventions, a small cross-tool semantic hint. Baseline 3 is correct when the schema does the heavy lifting.

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 the specific resource and payload: 'Search Console evidence for one website: action, gates, and landing-page rows.' This distinguishes it from a generic analytics snapshot by naming Search Console evidence, but it does not explicitly say how it differs from analytics_snapshot beyond shared parameter conventions, so it falls short of a 5.

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 explicit when-to-use or when-not-to-use guidance. The only cross-tool reference, 'Same from/to/time_zone/currency as analytics_snapshot,' is about parameter consistency rather than selecting this tool over alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources