Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Find pages losing Google clicks

insights_content_decay
Read-only

Pages that lost the most Google clicks: the last days compared with the days before. Pages with fewer than 10 clicks before are skipped.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteUrl": "<siteUrl>"
    },
    "name": "insights_content_decay"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLength of each period in days (7-90), ending 3 days before today because Search Console data lags. Defaults to 28.
limitNoMaximum results (1-200). Defaults to 25.
siteUrlYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description adds genuinely behavioral detail beyond them: results are ranked by click loss, and pages with fewer than 10 prior clicks are filtered out, which tells an agent why small pages will be absent from output.

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?

Two short sentences, the core ranking definition first and the exclusion rule second. Nothing is redundant or wasted.

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?

For a read-only, non-nested, three-parameter insight tool with no output schema, the definition covers the metric definition, ranking, and noise threshold. It leaves the shape of each result row (page, clicks lost, percent change) unspecified, but that is a modest gap.

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 coverage is 100%, so the schema already explains days, limit, and siteUrl in detail. The description reinforces that days defines two compared windows, slightly sharpening the comparative meaning, but adds no format, syntax, or constraint information beyond the schema.

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 states a specific resource and metric: pages that lost the most Google clicks, computed as a period-over-period comparison. This distinguishes it from generic siblings like gsc_performance_overview or insights_compare_periods, though it never names those alternatives explicitly.

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?

Usage is implied by 'lost the most clicks' — an agent can infer this is for diagnosing declining content — but there is no explicit when-to-use versus insights_compare_periods, gsc_search_analytics, or insights_striking_distance, nor any stated prerequisites beyond what the schema says about siteUrl.

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

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources