Skip to main content
Glama
Sign In
GSC SEO MCP

GSC SEO MCP

by samalyxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

performance_overview

Retrieve a site-level performance snapshot with period comparison, daily trends, device breakdown, and search appearance data.

Instructions

Return a site-level snapshot with previous-period comparison, daily trend, devices, and search appearances.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlNoGoogle Search Console property URL, e.g. sc-domain:example.com or https://www.example.com/.
startDateNoStart date in YYYY-MM-DD. If omitted, days is used.
endDateNoEnd date in YYYY-MM-DD. If omitted, days is used.
daysNoLookback window when startDate/endDate are omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It describes the output but does not mention data freshness, accuracy, permissions, pagination, or any side effects. The tool's internal logic (e.g., how previous period is computed) is opaque.

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?

The description is a single, clear sentence that directly conveys the tool's purpose with no unnecessary words.

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 lists output components but does not specify their format, structure, or how they are presented. For a tool with no output schema, more detail (e.g., fields returned, sorting, or aggregation) would be needed for reliable agent use.

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?

All parameters have schema descriptions (100% coverage), so the description adds little beyond implying date parameters relate to comparison and trends. The meaning of 'days' and its interaction with startDate/endDate is not clarified.

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 clearly states it returns a 'site-level snapshot' with specific components (previous-period comparison, daily trend, devices, search appearances), providing a precise verb and resource. However, it does not explicitly differentiate from siblings like 'compare_periods' or 'search_analytics', which may overlap in functionality.

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?

No guidance is provided on when to use this tool versus alternatives such as 'search_analytics' or 'compare_periods'. There is no mention of prerequisites, limitations, or typical use cases.

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

Deploy Server

Other Tools