Skip to main content
Glama

Управление списком промокодов

manage_promocode_group
Destructive

Правит списки промокодов: переименовывает список, меняет вид кода (текст, QR, штрихкод, DataMatrix) и его размер, удаляет список целиком, убирает отдельный код и привязывает список к другим опросам аккаунта. Завести список и досыпать кодов — это create_promocode_group и add_promocodes. Удаление списка уносит и все его коды, поэтому требует confirm_delete. Промокоды доступны не на всех тарифах.

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": {
      "quiz_id": "<quiz_id>",
      "action": "<action>"
    },
    "name": "manage_promocode_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoНовое название списка. Нужно для update.
actionYesЧто сделать: update — переименовать или сменить вид кода, delete — удалить список, attach — привязать список к опросам, detach — открепить список от опросов, delete_code — убрать один код.
code_idNoID промокода из get_promocode_codes. Обязателен для delete_code.
list_idNoID списка промокодов. Не нужен только для detach и delete_code.
quiz_idYesID опроса, от которого работаем: по нему проверяются права и тариф.
quiz_idsNoID опросов, до 200 за раз. Обязателен для attach и detach.
code_widthNoШирина кода в пикселях, 20–2000.
code_formatNoВид кода: text, qr, barcode, datamatrix.
code_heightNoВысота кода в пикселях, 20–2000.
confirm_deleteNoПодтверждение, что список удаляется вместе со всеми кодами.

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 destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description still adds real value: it states that deleting a list also destroys all of its codes and therefore requires confirm_delete, and it flags a plan-level availability constraint. It stops short of describing permission checks, partial-failure behavior when attaching to many quizzes, or any reversibility guarantees.

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 capability sentence is front-loaded, followed by sibling routing, then the destructive-consequence warning, then the plan constraint — a sensible priority order with no filler. The initial action enumeration is somewhat long and partly redundant with the action enum, which keeps it from being maximally tight.

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, multi-action, destructive tool with no output schema, the definition covers the essentials: what each action family does, what deletion destroys, the confirmation requirement, plan gating, and where the create/append work lives. Gaps remain around the 200-quiz batch limit consequences, permission requirements, and result/error shape, but the core calling decisions are supported.

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 including the action enum, list_id, code_id, quiz_ids and the code dimensions is already documented in structured form. The description largely restates that surface (code formats listed as 'текст, QR, штрихкод, DataMatrix' duplicate the enum) and adds no syntax, default, or interaction detail beyond it. Baseline 3 is appropriate.

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+resource ('Правит списки промокодов') and then enumerates the concrete mutations: rename, change code format/size, delete the whole list, remove one code, attach to other quizzes. It explicitly names the sibling tools that handle the adjacent operations (create_promocode_group, add_promocodes), so an agent can place this tool precisely in the family.

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?

It gives a clear routing rule for the most confusable siblings — creating a list or appending codes belongs to create_promocode_group and add_promocodes — plus a prerequisite (promocodes are not available on all plans) and a gate for the destructive path (confirm_delete required). What it does not do is disambiguate the internal action values (attach vs detach vs delete_code); that burden falls entirely on the schema enum.

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