Skip to main content
Glama

Xonta MAX

max_ad_report

Read-onlyIdempotent

Compare ad placements in MAX by real results: CPM, cost per click or bot start, cost per lead and per order, ROAS, profit after ads and ROMI (with margin), conversion with a 95% confidence interval. Says when a difference between channels may be chance and when there is too little data. A calculator only: it does not touch ad accounts or move money.

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": {
      "placements": "<placements>"
    },
    "name": "max_ad_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
eventsNoOptional bot_started updates, {'payload': …} objects or payload strings; starts are counted per placement id
campaignNoOnly count payloads of this campaign
min_ordersNoBelow this many orders a placement is flagged as low data
placementsYesPer placement: {name, id?, cost, views?, clicks?, starts?, leads?, orders?, revenue?, margin_pct?}

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 declare readOnly, idempotent, non-destructive and closed-world, and the description reinforces this by explicitly stating it does not touch ad accounts or move money. It adds real behavioral context beyond the annotations: statistical treatment at 95% confidence, detection of chance differences, and flagging of insufficient data. What is missing is any note on cost/limits or how large an input payload can be.

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?

Three sentences, front-loaded with the action and the output set, followed by a caveat sentence and a scope-limiter. The long metric list is dense but each item is a distinct computed figure, so it earns its space; no filler or restatement of the tool name.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so by naming the computed metrics and the confidence-interval/insufficient-data flags. A reader can anticipate the shape of the answer; only the exact response structure and per-placement output format remain unstated, which is a minor gap for a five-parameter calculator.

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 the schema already carries parameter meaning and a 3 is the baseline. The description adds only indirect signal — 'with margin' hints at margin_pct, and 'too little data' relates to min_orders — but it never explains required vs optional inputs or the events/campaign relationship beyond what the schema states.

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 opens with a specific verb and resource: 'Compare ad placements in MAX by real results', then enumerates the exact metrics produced (CPM, CPBC, CPBS, CPL, CPO, ROAS, profit after ads, ROMI, conversion with CI). This is unambiguous and clearly distinct from the sibling tools, which are API/message/scaffolding helpers rather than analytics calculators.

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?

'A calculator only: it does not touch ad accounts or move money' establishes a scope boundary and 'Says when a difference between channels may be chance and when there is too little data' implies the scenario (deciding whether channel differences are real). However, there is no explicit when-to-use/when-not guidance or named alternative, so usage must be inferred from the stated purpose.

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.