mcp-seo-audit

get_performance_overview

Read-onlyIdempotent

Retrieve Google Search Console performance totals and daily trends for a specified site and lookback period to monitor traffic changes and evaluate SEO results.

Instructions

Get a performance overview with totals and daily trend.

Args:
    site_url: Exact GSC property URL
    days: Number of days to look back (default: 28)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`site_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Apr 17, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the output shape ('totals and daily trend'), which is mild behavioral context, but says nothing about auth requirements, rate limits, or data freshness beyond what annotations provide.

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?

The purpose is front-loaded in one sentence, and the argument list is terse and wastes no words. The 'Args:' block is slightly boilerplate but not verbose.

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?

An output schema exists, so return values need not be explained. What is missing given the crowded sibling set is any differentiation or usage context, which leaves the agent to guess among several analytics tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden and largely does: it clarifies site_url is the 'Exact GSC property URL' and that days is a lookback window defaulting to 28. It stops short of giving the site_url format (e.g. sc-domain: prefix) that would fully disambiguate input.

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 a specific verb and resource ('Get a performance overview') and reveals the payload shape ('totals and daily trend'). However, it does nothing to separate itself from siblings like get_search_analytics, get_advanced_search_analytics, or get_search_analytics_snapshot, which an agent could easily confuse it with.

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, no prerequisites, and no mention of alternatives. With four sibling analytics tools in the list, the absence of any routing signal is a real gap.

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

Deploy Server