Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc analyze search appearance trends

gsc_analyze_search_appearance_trends

Read-onlyIdempotent

Analyze rich result and structured data appearance trends in Google Search Console, comparing current and previous periods to identify performance shifts.

Instructions

Analyze structured data and rich-result trend signals via the Search Analytics searchAppearance dimension when GSC exposes it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topN`	No	Maximum number of highest-ranked results to return.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`sortBy`	No	Metric or dimension used to rank the returned results.	impressionsDelta
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.	last28days
`searchType`	No	Search surface to report, such as web, image, video, news or Discover. Availability depends on the property.	web
`includePages`	No	When true, groups by searchAppearance + page for page-level rich result trends.
`minImpressions`	No	Minimum reported impressions required for a row to enter the analysis.
`currentDateRange`	No	Current period. Defaults to datePreset.
`previousDateRange`	No	Previous period. Defaults to the immediately preceding period with the same length.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add behavioral context beyond that. It adds a useful conditional-availability caveat, but does not describe behavior on unsupported properties, pagination, or empty results. This is adequate but not rich.

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 concise sentence with the core action and key caveat front-loaded. There is no filler, and every clause contributes to understanding the tool's purpose.

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 schema and output schema carry most of the load for this 10-parameter tool. The description supplies the core purpose and an availability caveat, but it does not address how to select among sibling analytics tools or what happens when GSC does not expose searchAppearance. It is adequate with clear gaps.

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 100%, so all 10 parameters are documented in the schema itself. The description adds no parameter-level detail, so the baseline of 3 applies.

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 identifies the action ('analyze'), the resource ('structured data and rich-result trend signals'), and the mechanism ('Search Analytics searchAppearance dimension'). It distinguishes itself from generic query tools by naming a specific dimension, though it does not explicitly contrast with sibling tools.

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 phrase 'when GSC exposes it' implies an availability condition and suggests the tool should not be used when the dimension is unavailable. However, it does not explicitly state when to prefer this over gsc_query_search_analytics or gsc_compare_search_types, leaving the selection largely implied.

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