Skip to main content
Glama

max_deeplink

Read-onlyIdempotent

Build and validate MAX deep links for bots, mini-apps, mentions, or share buttons, with payload length and character checks to prevent silently dropped messages.

Instructions

Build and validate MAX deep links. 'share' gives a link, an HTML button and a JS helper that open MAX's chat picker with prefilled text — works on any website or AI agent output without owning a bot. Payload limits are checked, because MAX silently drops payloads that are too long or have bad characters.

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": {
      "kind": "<kind>"
    },
    "name": "max_deeplink"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesstart — open bot with payload; startapp — open mini-app; share — 'send to MAX' link for any site, no bot needed; mention — user mention markup
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
textNoshare: text to prefill; mention: display name
payloadNostart: ≤128 chars; startapp: ≤512, A-Za-z0-9_- only
user_idNomention: MAX user id
bot_nameNoBot public name as in max.ru/<name> (start, startapp)
button_labelNoshare: label for the generated HTML button; default depends on lang

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely non-obvious context beyond them: payload limits are actively validated because MAX silently drops over-long or malformed payloads — a failure mode an agent could not infer from annotations. It doesn't state what a validation failure returns, which keeps it from a 5.

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 the action, and the payload-limit caveat is placed where it will be read before constructing a call. No filler or restated name/title phrasing.

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 7 parameters, full schema coverage and no output schema, the essentials are present, but the description is effectively written only for the 'share' kind. An agent calling with kind='mention' or 'startapp' gets no behavioral context from the description about what is returned or what validation applies to those modes.

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 every parameter (kind, lang, text, payload, user_id, bot_name, button_label) is already documented with per-kind semantics and constraints. The description reinforces the payload-limit rationale but adds no new syntax or per-parameter meaning beyond the schema, so baseline 3 applies.

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 opening sentence gives a specific verb+resource ('Build and validate MAX deep links'), and the description explains what the 'share' variant produces (link, HTML button, JS helper). It stops short of describing all four kinds equally — 'mention' and 'start'/'startapp' outputs are left entirely to the schema — but the core purpose is unambiguous.

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?

It implicitly distinguishes the 'share' kind by noting it works 'on any website or AI agent output without owning a bot', which is useful selection context within the tool. However, it offers no guidance on when to use this tool versus siblings such as max_build_message or max_tracking_links, and no prerequisites or exclusions are stated.

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