Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

Удалить группы

delete_ad_groups
Destructive

Permanently deletes Yandex.Direct ad groups by their IDs. Use it to remove groups that are no longer needed; deletion cannot be undone.

Instructions

Удалить группы объявлений по их ID. ⚠️ Необратимо.

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

Input Schema

NameRequiredDescriptionDefault
ad_group_idsYesГруппы, которые будут удалены безвозвратно

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      +  "type": "boolean"
      +}
  3. First observedv1.6.1

TDQS

A3.5/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 openWorldHint=true, so the safety profile is covered by structured data; the description's 'Необратимо' adds an explicit confirmation of permanence. It does not disclose the important behavioral consequence — whether contained ads and keywords are removed with the group — nor error handling for unknown or already-deleted IDs. That is a modest addition over annotations, hence a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, purpose first and the destructive warning second, with zero filler. Nothing in the text could be removed without losing information.

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 an irreversible bulk-delete with no output schema, an agent still lacks the cascade story (are child ads/keywords deleted?), behavior when some IDs are invalid, and confirmation that deletion is atomic or per-item. The warnings present are accurate but the picture is incomplete for a destructive operation.

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 coverage is 100% and both the array and its item pattern/format are documented in the schema, including 'Группы, которые будут удалены безвозвратно'. The description only restates 'по их ID' and adds no batch-size, ordering, or partial-failure semantics, so baseline 3 applies.

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?

States a specific verb ('Удалить') plus resource ('группы объявлений') and the selector ('по их ID'), which cleanly separates it from destructive siblings such as delete_ad_extensions, delete_sitelinks and delete_vcards. An agent can identify exactly what entity this removes without consulting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus update_ad_group or manage_campaigns, and no stated prerequisites or alternatives. The only usage signal is the irreversibility warning, which cautions but does not route the agent.

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