Skip to main content
Glama

Короткие ссылки школы

list_short_links
Read-onlyIdempotent

Короткие ссылки школы, новые сверху: короткий адрес, куда ведёт (адрес или бот с кодом воронки), площадка, ролик или кампания, метки и цифры за последние 30 дней в stats_30d: clicks (переходы), people (разные люди), to_bot (пришли в бота), leads (заявки), deals (сделки), payments (оплаты), revenue (рубли, строкой).

Отбор: q ищет в названии, адресе, кнопке, имени бота и пути; platform: youtube, vk, rutube, telegram, instagram, tiktok, direct, email, site, other; set_id: ссылки одного ролика или кампании; archived=true: архив. Например, «какая ссылка под роликами YouTube принесла больше денег»: platform=youtube, затем сравнить stats_30d.revenue. Не больше 200 за раз, дальше offset; total показывает, сколько всего.

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": "list_short_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo
offsetNo
set_idNo
archivedNo
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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, closed-world behavior, and the description adds real context beyond them: rows are ordered newest-first, results are capped at 200 per call with offset paging, total reports the full count, and stats_30d is a rolling 30-day window with named metrics and rubles-as-string. Return field meanings are the main gap, though that is partly a schema concern.

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?

The scope and ordering come first, then return fields, then filters, then the worked example — a sensible front-loaded order with no filler sentences. The metric glossary is dense but each term maps to a real field, so little could be cut without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter descriptions, the description compensates fully: it describes the shape of returned rows, the stats_30d metric set, the filter vocabulary, and the pagination contract. An agent could call and interpret this tool correctly from the description alone.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: it defines q's search scope (title, address, button, bot name, path), enumerates the platform vocabulary that the schema does not encode as an enum, explains set_id as grouping links of one video/campaign, and clarifies archived=true meaning plus the 200-per-page ceiling for limit/offset. This is meaning the schema cannot supply on its own.

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 states a specific verb and resource ('Короткие ссылки школы, новые сверху') and immediately enumerates what each row contains, so the agent knows this is a paginated list of tracked links rather than a per-link stats call. It stops short of naming the sibling it is not (e.g. get_link_stats), so differentiation is inferred from content rather than stated.

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?

The 'Отбор' block explains what each filter does, lists the accepted platform values, and gives a concrete worked example ('какая ссылка под роликами YouTube принесла больше денег': platform=youtube, затем сравнить stats_30d.revenue). It never states when to prefer a different tool, but the usage context is otherwise explicit.

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