Skip to main content
Glama

Why revenue moved

revenue_moves
Read-onlyIdempotent

Why revenue moved for one website: the window against the same-length prior window, split into new and renewal revenue, the channels, landing pages, search queries and referrer hosts (any site, not only AI) that moved it (the top 5 per group; search_query is estimated from Search Console), and which sources over-index among new payers. Same from/to/time_zone/currency as analytics_snapshot. Quote summary and the movers; do not recompute them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revenue_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoinclusive end YYYY-MM-DD; default today
fromNoinclusive start YYYY-MM-DD; default last 60 days
periodNonamed window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month
currencyNolowercase ISO 4217 code
time_zoneNoIANA time zone; default UTC
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real behavior: the comparison basis is a same-length prior window, results are capped at the top 5 per group, search_query is estimated from Search Console (a data-quality caveat), and referrer hosts cover any site, not just AI. The 'do not recompute' instruction also tells the agent the output is authoritative rather than raw material.

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 the opening clause, and the description is dense with specifics rather than filler. The first sentence is long and list-heavy, but nearly every clause carries information an agent needs, so the density is justified rather than wasteful.

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?

Six optional parameters, a full output schema, and rich annotations mean the description need not explain return values, yet it does explain the breakdown structure, which is helpful framing. It covers comparison basis, result caps, and data provenance; the only gap is the absence of explicit routing versus sibling diagnostic tools.

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 six parameters are already documented, including enums for period and defaults for from/to/time_zone. The description adds only that from/to/time_zone/currency behave the same as in analytics_snapshot, which is a mild consistency note rather than new semantic detail, so the baseline 3 applies.

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 gives a specific verb-and-resource statement: it explains revenue movement for one website by comparing the window to an equal-length prior window. It then enumerates exactly what the breakdown contains (new vs renewal revenue, channels, landing pages, search queries, referrer hosts, over-indexing sources), so an agent can distinguish it from analytics_snapshot or money_leaks without opening a schema.

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 rather than stated: the phrasing 'why revenue moved' signals a diagnostic use case, and 'Quote summary and the movers; do not recompute them' is an instruction on handling the output. However, the description never says when to pick this over analytics_snapshot (referenced only for parameter parity), insights, or money_leaks, and it names no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources