Skip to main content
Glama

MetricPort

Weekly SEO report

gsc_weekly_report
Read-onlyIdempotent

One call for a client-ready weekly summary: totals vs. previous week, top winners and losers (pages and queries), new queries, top 5 quick wins and anomalies. Optional brandPattern adds a brand/non-brand split.

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": {
      "property": "<property>"
    },
    "name": "gsc_weekly_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNo
propertyYesSearch Console property id from list_properties, e.g. sc-domain:example.com or https://www.example.com/
brandPatternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. With no output schema, the description usefully carries the return-content burden by naming the report sections, and it discloses that brandPattern changes the output shape (adds a brand/non-brand split). It does not state how the reporting window is derived or any data-freshness/rate-limit caveats.

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 tightly written sentences, front-loaded with the core promise ('One call for a client-ready weekly summary') followed by the content list. No filler or redundancy.

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?

For a read-only, annotation-covered report tool with no output schema, the description is nearly complete: it tells the agent what comes back and the optional brand split. The remaining gap is the endDate/reporting-window semantics, which neither the schema nor the description explains.

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 only 33% (only 'property' is documented). The description partially compensates by explaining brandPattern's effect ('Optional brandPattern adds a brand/non-brand split'), but endDate is left entirely unexplained in both schema and description, so how the weekly window is anchored is never stated.

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

Purpose5/5

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

States a specific verb and resource ('client-ready weekly summary') and then enumerates exactly what it aggregates: totals vs. previous week, winners/losers for pages and queries, new queries, quick wins, anomalies. That content list implicitly maps to and distinguishes it from the atomic siblings (gsc_top_pages, gsc_quick_wins, gsc_new_and_lost_queries, gsc_brand_split), so an agent can tell this is the consolidated report rather than a single-metric tool.

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?

'One call for a client-ready weekly summary' implies the reporting use case, but the description never states when to prefer this over the granular sibling tools, nor any exclusions or prerequisites (e.g. needing a valid property first). Usage is inferable but not spelled out.

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.