Skip to main content
Glama

Xonta MAX

max_tracking_links

Read-onlyIdempotent

Make a separate tracking link (and promo code) for every channel where an ad is placed in MAX, so you can see which placement brought users and sales. Bot links use ?start=: the id arrives in bot_started.payload, which works even for clicks that never leave the messenger. Returns a media plan as CSV. Then feed the counts to max_ad_report.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
bot_nameNoYour bot's public name: each placement gets max.ru/<bot>?start=<id>
campaignYesCampaign name, e.g. 'black friday'
site_urlNoLanding page: each placement gets UTM tags and its erid
placementsYesChannels where the ad goes: [{name, cost?, erid?}]. name may be a title or max.ru link
utm_mediumNoseeding
promo_codesNoAlso make one promo code per placement
mini_app_botNoBot with your mini-app: each placement gets ?startapp=<id>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context on top: how bot links are formed (?start=<id>), that the id surfaces in bot_started.payload and survives clicks that never leave the messenger, and that the return is a CSV media plan. It stops short of covering edge cases such as invalid placement names or duplicate ids.

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 tight sentences: purpose, then mechanism, then output and hand-off. The purpose and the payoff are front-loaded. A small amount of density in the middle sentence (payload/bot_started detail) is justified because it explains a non-obvious mechanism.

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 8 parameters, no output schema, and a generative/read-only tool, the description covers the essential gaps: what is produced (CSV media plan with links and promo codes), the mechanism, and the follow-up tool. It leaves minor questions unanswered, such as what happens when a placement name cannot be resolved or whether existing links are regenerated, but nothing critical is missing for correct invocation.

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 88%, so the schema already documents lang, bot_name, site_url, mini_app_bot, placements, promo_codes and utm_medium, including the ?startapp=<id> and erid behavior. The description restates the ?start=<id> mechanism rather than adding new per-parameter meaning, 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 opens with a specific verb and resource: 'Make a separate tracking link (and promo code) for every channel where an ad is placed in MAX.' It goes beyond that by naming the concrete deliverable ('Returns a media plan as CSV') and by routing to the sibling that consumes the result ('feed the counts to max_ad_report'), so an agent can distinguish it from max_deeplink and max_ad_report 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is strongly implied by the outcome statement ('so you can see which placement brought users and sales') and the explicit downstream step 'Then feed the counts to max_ad_report,' which establishes the workflow order with a sibling. There is no explicit when-not-to-use (e.g. single-placement or non-ad use cases), which keeps it out of the 5 tier.

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.