Skip to main content
Glama

ADS Beast

analytics_compare_periods

Read-only

Percentage change of every KPI between the current period and the one before it, by platform, with what got worse and what improved.

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": {
      "client_id": "<client_id>"
    },
    "name": "analytics_compare_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idYes
current_daysNoLength of the current period in days.
previous_daysNoLength of the preceding period in days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without help from the description. The description usefully adds that results include both regressions and improvements across all KPIs, but says nothing about cost, latency, empty-period handling, or whether periods must be contiguous.

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?

A single front-loaded sentence that leads with the computation and its scope, with no filler. The trailing clause 'with what got worse and what improved' is informative about output but slightly informal compared to the precision of the preceding clause.

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?

With no output schema, the description carries the burden of describing returns, and it only gestures at them ('every KPI', 'what got worse and what improved') without naming the KPI set or shape. For a four-parameter read-only tool this is workable, but an agent cannot predict the response structure or how it behaves when a period has no data.

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 75%, so the schema already documents platform values and both day-length parameters with defaults. The description only adds the relational meaning that the two windows are adjacent ('the one before it'), which is genuinely useful but is the sole contribution beyond structured fields; client_id remains undescribed in both places.

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 names a specific computation (percentage change per KPI) plus both its scope (current vs. preceding period) and its dimension (by platform), which is far more than a restatement of the tool name. It does not explicitly name a contrasting sibling such as analytics_kpi_health, so differentiation is left to inference rather than stated.

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 the phrase 'between the current period and the one before it', which tells an agent this is a period-over-period comparison tool. However, there is no explicit when-to-use or when-not-to-use guidance, and no pointer to the adjacent tools (analytics_summary, analytics_kpi_health, analytics_growth_opportunities) that overlap with it.

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.