Skip to main content
Glama

ADS Beast

analytics_forecast

Read-only

Projection of CPA, ROAS and spend 7 and 30 days ahead from the current trend. A projection, not a promise: it extrapolates the last 14-30 days.

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_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
campaign_idNoADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the extrapolation basis (last 14-30 days) and an explicit uncertainty caveat ('a projection, not a promise'). It stops short of describing output shape or how client-level versus campaign-level scoping changes results.

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 sentences, front-loaded with what is projected and over what horizon, followed by a single caveat sentence. Every clause carries information and there is no filler.

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 simple read-only forecast with no output schema, the description covers metrics, horizons, extrapolation window and uncertainty, which is most of what an agent needs. The main gap is parameter scoping (client-level versus campaign-level) and the undocumented required client_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: campaign_id is documented in the schema, but the required client_id has no description anywhere. The description does not mention either parameter, so it fails to compensate for the undocumented required field or explain how scoping to a campaign versus a client affects the forecast.

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 the specific metrics (CPA, ROAS, spend) and the exact horizons (7 and 30 days), so the agent can tell this is a forward-looking projection rather than a historical report. It does not explicitly differentiate itself from siblings such as analytics_summary or analytics_compare_periods, so it falls short of a 5.

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 'from the current trend' and the note that it extrapolates the last 14-30 days implies when the tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for historical or actuals data. Usage is inferable but not stated.

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.