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

yandex-direct-mcp-plus

by Pavelsiba

Удалить списки ретаргетинга

delete_retargeting_lists
Destructive

Delete retargeting and audience conditions by ID; removal is irreversible, and per-condition refusals are returned as ❌ while other conditions are still deleted.

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": {
      "retargeting_list_ids": "<retargeting_list_ids>"
    },
    "name": "delete_retargeting_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
retargeting_list_idsYesУсловия, которые нужно удалить; ID берутся из list_retargeting_lists

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.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so irreversibility is partly redundant, but the description adds genuinely new behavior: per-item refusals come back as ❌ strings while the remaining items are still deleted. That partial-failure contract is not derivable from the annotations or schema and materially changes how an agent should interpret the call.

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 short sentences, with the destructive scope front-loaded ahead of the partial-failure note. Nothing is repeated and every clause adds information.

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, single-parameter batch tool with no output schema, the description covers scope, irreversibility, and the response shape for refused items. Minor gaps remain around auth requirements and whether unknown or already-deleted IDs count as refusals.

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?

The single parameter has 100% schema description coverage including the ID-source hint and the minItems/maxItems bounds, so the schema carries the detail. The description only restates 'by ID' and adds no format or batching semantics beyond what the schema already provides, which is the baseline 3.

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 description states a specific verb and resource in Russian ('Удалить условия ретаргетинга и подбора аудитории по ID'), which is unmistakably distinct from the add/update/list siblings. It does not explicitly name those siblings, but the destructive verb alone is enough to disambiguate.

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 only implied: delete conditions whose IDs come from list_retargeting_lists. There is no explicit statement about when to use this versus update_retargeting_lists, and no prerequisites or when-not-to-use guidance beyond the irreversibility warning.

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