Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search appearance / rich results report

gsc_rich_results_report
Read-onlyIdempotent

Analyze clicks and impressions by Google search appearance type, from rich results to Discover. Identify top pages per appearance type to optimize search visibility.

Instructions

Show how the site appears in Google results: clicks and impressions per search appearance type (rich results, FAQ, review snippet, video, AMP, translated results, Discover...), and the top pages for each appearance type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateNoEnd: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).3daysAgo
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
startDateNoStart: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).90daysAgo
searchTypeNoSearch appearance data mostly exists for 'web'; other types can come back empty.web
pagesPerTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / searchType
      Added value: +{
+  "default": "web",
+  "description": "Search appearance data mostly exists for 'web'; other types can come back empty.",
+  "enum": [
+    "web",
+    "image",
+    "video",
+    "news",
+    "discover",
+    "googleNews"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."New value: +"Search Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites)."
  2. Changed4 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / endDate / description
      Previous value: -"End date: YYYY-MM-DD, 'today', 'yesterday' or 'NdaysAgo' (e.g. '28daysAgo'). Search Console data lags ~2-3 days."New value: +"End: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days)."
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Property URL exactly as shown in Search Console, e.g. 'https://example.com/' or 'sc-domain:example.com'. Use gsc_list_sites to discover it."New value: +"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."
    • changedInput schema / properties / startDate / description
      Previous value: -"Start date: YYYY-MM-DD, 'today', 'yesterday' or 'NdaysAgo' (e.g. '28daysAgo'). Search Console data lags ~2-3 days."New value: +"Start: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days)."
  3. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds no further behavioral details beyond what annotations imply, such as data lag or limitations. It does not contradict annotations, but it also does not enrich them with context like auth requirements or rate limits.

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, efficient sentence that front-loads the core purpose and includes concrete examples of appearance types. There is no redundancy or filler, making it appropriately sized and well-structured.

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 the moderate complexity (5 parameters, no output schema), the description covers the main output (clicks/impressions per type, top pages) and purpose. It does not mention data lags or searchType limitations, but these are already documented in the schema descriptions. The description is sufficiently complete for an agent to understand the tool's scope and output shape.

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 80%, so the baseline is 3. The description does not elaborate on parameter semantics beyond what the schema already provides. It mentions 'appearance type' but does not clarify parameter usage or add value beyond the schema's own descriptions.

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?

The description clearly states the verb 'Show' and the resource (how the site appears in Google results), with specific metrics (clicks and impressions) and categories (rich results, FAQ, review snippet, etc.). It distinguishes itself from sibling tools like gsc_search_analytics by focusing on appearance types, making it unambiguous.

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?

The description explains what the tool does but does not explicitly state when to use it versus alternatives. It lacks guidance on scenarios where other GSC tools (e.g., gsc_search_analytics) would be more appropriate. While the focus on appearance types implicitly differentiates it, explicit usage guidelines are missing.

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