Skip to main content
Glama
Yandex Direct MCP

Yandex Direct MCP

Удалить группы объявлений

delete_ad_groups
Destructive

Deletes ad groups by ID, permanently removing their ads and keywords; this action cannot be undone.

Instructions

Удаляет группы объявлений по id (adgroups/delete). Вместе с группой удаляются её объявления и ключевые фразы; отменить это нельзя. Запрос идёт в API v501, в песочнице — в v5.

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": {
      "ids": "<ids>"
    },
    "name": "delete_ad_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesId групп, которые нужно удалить.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / client_login
      Added value: +{
      +  "description": "Логин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.",
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._@-]{0,99}$",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / ids / description
      Previous value: -"Ad group ids to delete."New value: +"Id групп, которые нужно удалить."
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only flag destructive/non-idempotent), it discloses the cascade ('Вместе с группой удаляются её объявления и ключевые фразы') and irreversibility ('отменить это нельзя'), plus the API version routing including sandbox v5 — exactly the behavior an agent needs before an irreversible write.

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?

Three short sentences, front-loaded with the action and followed by the consequence, then version routing; no filler.

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 destructive, two-parameter mutation with no output schema, the description covers consequences, irreversibility, and environment routing. It does not address partial-failure behavior or what ids are returned, a minor gap.

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 ids and client_login are already documented in the schema; the description only reinforces that deletion is by id and adds no new meaning for client_login resolution beyond re-stating it.

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 states a specific verb and resource ('Удаляет группы объявлений по id (adgroups/delete)'), names the endpoint, and makes clear this is a bulk delete by identifier, which separates it cleanly from list_ad_groups and the create/update siblings.

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?

Usage is implied by the verb 'delete' and the required ids array, but there is no explicit guidance on when to prefer this over other destructive siblings (e.g. campaign_action/ad_action) or what preconditions exist (e.g. ad group must belong to the caller's account).

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