Skip to main content
Glama

max_tracking_links

Read-onlyIdempotent

Creates a separate tracking link and promo code for each MAX ad placement, so you can identify which channel drove users and sales, then exports a CSV media plan for reporting.

Instructions

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 observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral detail beyond them: the ?start=<id> mechanism, that the id arrives in bot_started.payload, that it works for clicks that never leave the messenger, and that the output is a media plan CSV.

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?

Front-loaded with the core action and mechanism, then the return format and the handoff to max_ad_report. Dense but every sentence carries information; minor tightening possible.

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 an 8-parameter tool with no output schema, the description covers the mechanism, the return format (CSV), and the follow-up tool. It leaves some parameter-level nuance to the schema, which is acceptable given 88% coverage.

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

Parameters4/5

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

Schema coverage is already 88%, and the description still adds meaning: bot_name maps to max.ru/<bot>?start=<id>, mini_app_bot to ?startapp=<id>, and site_url drives UTM tags and erid. It reinforces rather than merely repeats the schema.

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?

States a specific verb and resource ('Make a separate tracking link (and promo code) for every channel where an ad is placed in MAX') and clarifies the downstream relationship to max_ad_report, so an agent can distinguish it from the reporting sibling.

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?

Gives clear context for when to use it (per-placement tracking for MAX ads) and names the follow-up tool ('Then feed the counts to max_ad_report'). It does not state when-not to use it or prerequisites, so it falls short of a full 5.

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