Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

get_page_performance

Retrieve Google Search Console totals and the queries driving traffic for a single URL over a chosen period to diagnose page performance.

Instructions

Full GSC picture for one URL: totals + the queries driving it.

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": "get_page_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
siteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only retrieval but says nothing about defaults (28-day window, empty url default), what happens when url is omitted, whether a site/property must be resolved first, or any rate/auth constraints. Only the output shape is covered elsewhere, so behavior is largely undisclosed.

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?

One short sentence, front-loaded with the scope and followed by the return contents; nothing is wasted. It is arguably over-terse rather than padded, but it is structurally sound.

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?

The presence of an output schema means return values need not be spelled out, and the description correctly conveys the two-part result. However, with three undocumented optional parameters and no annotations, the definition is not complete enough for confident invocation—the agent must guess about site and days.

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 0% across three parameters, so the description must compensate and does not. 'for one URL' hints at the url parameter, but days (window length), site (nullable property selector), and the fact that all three are optional with defaults are never explained. An agent cannot infer the meaning of the site parameter or the effect of its null default.

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 concrete resource (GSC performance) and a specific scope (one URL), plus what comes back (totals and driving queries). It is a clear verb-less but understandable statement of purpose. It does not differentiate from the near-identical sibling get_raptive_page_performance, which leaves real ambiguity about which page-performance tool to pick.

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 when-to-use guidance at all: no statement of prerequisites (does 'site' need to be set?), no exclusions, and no routing to alternatives such as get_raptive_page_performance or list_sites. Given a sibling with almost the same name, the absence of differentiation is a significant gap.

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