Skip to main content
Glama

Завести короткую ссылку

create_short_link

Короткая ссылка на домене школы: на адрес (url) или в бота (bot_username и, если нужно, start_code: код воронки «Старта»). platform (youtube, vk, rutube, telegram, instagram, tiktok, direct, email, site, other) ставит метки сама: utm_source, utm_medium, utm_campaign; свои метки (utm: source, medium, campaign, content, term) главнее. path: свой путь латиницей; без него система выберет понятный, варианты покажет suggest_link_path. button: подпись кнопки под роликом, set_id: ролик или кампания школы.

Та же ссылка (тот же адрес или бот с кодом, та же площадка, кнопка и ролик) второй раз не заводится: вернётся прежняя, created=false. Например: url https://it-ontime.ru/mikrotik, platform youtube → short_url https://go.it-ontime.ru/mikrotik, метки youtube, video, mikrotik. Ошибка (путь занят, адрес не тот, нет домена) приходит ответом 400 с текстом для человека.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_short_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
utmNo
pathNo
titleNo
buttonNo
set_idNo
platformNo
start_codeNo
bot_usernameNo
Idempotency-KeyNoКлюч повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Idempotency-Key
      Added value: +{
      +  "description": "Ключ повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses real behavior: automatic UTM tagging with an override precedence, default path selection, content-based de-duplication returning created=false, and a 400 error carrying a human-readable message for occupied paths or bad addresses. There is mild tension with idempotentHint=false, since re-creating an identical link returns the earlier one rather than making a second object, though that is content de-duplication rather than call-level idempotency. Auth/permission requirements and rate limits are not mentioned.

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?

Purpose is front-loaded, followed by parameters, then idempotency, a concrete example, and error behavior — a sensible order. The middle section is telegraphic and noun-heavy, compressing several parameters into parenthetical fragments, but nearly every sentence carries decision-relevant information.

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 10-parameter creation tool with no output schema, the description supplies the return shape (short_url, created=false on duplicate) and the failure shape (400 with human text), plus a worked example. The remaining gaps are the undocumented title parameter and the unmentioned Idempotency-Key retry contract, which the schema partly covers.

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 description coverage is only 10%, so the description carries most of the load and largely does: it explains url vs bot_username/start_code, the platform value set (enumerated in prose since the schema has no enum), the auto-generated vs caller-supplied utm keys with precedence, path, button, and set_id. The title parameter is never explained, and the Idempotency-Key parameter is left entirely to its schema description.

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 opening states a specific verb and resource (create a short link on the school domain) and immediately scopes it to two modes: to a URL, or to a bot via bot_username plus start_code. It also routes one sub-decision to the sibling suggest_link_path, so an agent can distinguish this tool from that one without reading either 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 spelled out conditionally: use url for a direct address, use bot_username (+ optional start_code for a funnel) for a bot link, and rely on suggest_link_path when no custom path is supplied. It also says when not to expect a new object (same address/bot code/platform/button/set returns the existing link). No explicit guidance about update_short_link or list_short_links, so a sibling routing gap remains.

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.

Resources