Skip to main content
Glama
Suganthan-Mohanadasan

Google Search Console MCP Server

by Suganthan-Mohanadasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

image_content_decay

Flags pages with a consistent decline in image-search clicks across three 30-day windows. Uses a lower threshold suited to image search to surface meaningful declines from lower image-search volumes.

Instructions

Image-search version of content_decay. Three 30-day windows, flags pages with a consistent decline across all three. Defaults to a lower minimum click threshold than the web equivalent because image search produces lower click volumes overall. IMPORTANT: Base your analysis ONLY on the data returned. Report exact numbers from the results. Do not speculate about causes (e.g. algorithm updates, competitor actions) unless the data explicitly supports it. If the data does not contain enough information to answer a question, say so clearly rather than guessing. PRESENTATION: Always present these results as a rich, interactive visualization using artifacts. Use summary cards for key metrics, colour-coded indicators for severity or change direction (green for positive, red for negative), bar charts or sparklines for comparisons, and tabbed sections to organise different categories of results. Make the output visually scannable and dashboard-like rather than plain text or raw tables. POSITION: position is an impression-weighted average over real impressions, blended across queries, devices and countries. It is not a rank-tracker rank. Deep positions are only recorded when a user actually reaches that part of the results, so values beyond page one rest on sparse data. Treat absolute positions as directional and prefer position deltas between periods when judging change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlNoOverride the configured property (e.g. sc-domain:example.com or https://www.example.com/)
min_period3_clicksNoMinimum image-search clicks in the oldest 30-day window required for a page to be considered

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.1
    • addedInput schema / properties / site_url
      Added value: +{
+  "description": "Override the configured property (e.g. sc-domain:example.com or https://www.example.com/)",
+  "type": "string"
+}
  2. Addedv2.4.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations to rely on, the description carries the full behavioral burden and does so thoroughly. It warns against speculating about causes, requires exact-number reporting, instructs the agent to explicitly acknowledge insufficient data, clarifies the nuanced meaning of position, and specifies presentation expectations. This is far beyond what the schema or name alone would convey.

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 description is longer than average, but it is logically structured with separate IMPORTANT, PRESENTATION, and POSITION sections. The core purpose is front-loaded, and the additional detail is operationally useful rather than filler. It could be trimmed slightly, but the structure earns its place for a complex analytics tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, the description provides nearly everything an agent needs: the exact analysis methodology, data interpretation caveats, guardrails on speculation, and presentation requirements. It is complete enough to call the tool correctly and handle the returned data appropriately.

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 coverage is 100%, so the schema already documents both parameters. The description adds value by explaining why the min click threshold is lower for image search, which helps an agent interpret min_period3_clicks. It does not substantially add to site_url, but the schema covers it fully.

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 identifies this as the image-search variant of content_decay and states the exact detection heuristic: three 30-day windows with consistent decline across all three. It also distinguishes itself from the web equivalent through its lower minimum click threshold, so an agent can tell it apart from 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context that this is the image-search version of content_decay and explains the threshold difference from the web equivalent. However, it does not explicitly state when an agent should choose this tool over content_decay or when not to use it, leaving the routing decision partially implicit.

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