Skip to main content
Glama

Метки партнёрских источников

manage_partner_source
Destructive

Заводит, переименовывает и удаляет метки источников партнёрской ссылки. Метка отделяет один канал продвижения от другого: по ней в статистике видно, откуда пришёл человек. Сами метки и статистику по ним показывает get_partner_program. Метки принадлежат партнёру, а не аккаунту.

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

Input Schema

NameRequiredDescriptionDefault
nameNoНазвание метки, от 3 до 25 символов. Обязательно для rename; при create без него подставится имя по порядку.
actionYesЧто сделать: create — завести метку, rename — переименовать, delete — удалить.
source_idNoID метки из get_partner_program. Нужен для rename и delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the agent knows this mutates data. The description adds the ownership nuance (labels belong to the partner, not the account), which is genuinely beyond the annotations. However, it doesn't say what happens to existing statistics when a label is deleted, which is the main risk for an irreversible operation.

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?

Four short sentences, front-loaded with the operations and followed by the concept, the read alternative, and the ownership scope. Nothing is redundant, though the middle explanatory sentence is slightly longer than strictly necessary.

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?

For a 3-parameter mutation tool with full schema coverage and annotations, the description covers purpose, ownership and the read counterpart. It stops short of describing the consequences of deletion (statistics loss, whether a label can be removed while still in use), which matters given destructiveHint=true, so it is adequate but not complete.

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%, and the schema itself documents the 3–25 character name bound, the create/rename/delete enum, and that source_id comes from get_partner_program. The description adds no syntax or format detail beyond that, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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 names specific verbs and the resource: it creates, renames and deletes partner-link source labels. It also explains what a label is (it separates promotion channels and shows up in statistics), which lets an agent distinguish it from get_partner_program, the read-only 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?

It clearly points to get_partner_program for viewing labels and their statistics, establishing the write-vs-read split. It also states labels belong to the partner rather than the account, which is a useful scoping prerequisite. It doesn't spell out per-action preconditions, such as whether a label must be empty before deletion, but the action enum in the schema covers which operation to pick.

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