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

yandex-direct-mcp-plus

by Pavelsiba

Удалить уточнения

delete_ad_extensions
Destructive

Permanently removes ad extensions by their IDs. Use it to clear unwanted callouts or sitelinks from Yandex.Direct ads; deletions 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_extension_ids": "<ad_extension_ids>"
    },
    "name": "delete_ad_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_extension_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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's "⚠️ Необратимо" restates what structured data provides rather than adding to it. It says nothing about what happens to extensions still attached to ads, whether partial failures are possible in a batch of up to 1000 IDs, or what permissions are required.

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?

Two short sentences with the action front-loaded and the irreversibility warning placed second, which is a sensible order. Nothing is padded, though the content is close to the minimum rather than richly informative.

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 simple one-parameter delete with no output schema and destructive annotations already present, the essentials are covered. However, batch semantics (up to 1000 IDs deleted in one call) and failure behavior on partially invalid IDs are absent, which an agent would want before invoking a destructive bulk 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?

There is a single parameter and schema description coverage is 100%, with the schema already documenting the array of extension IDs, the 1–1000 item bounds, and the numeric-string pattern. The description's "по ID" adds no meaning beyond that, so the baseline of 3 applies.

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 ("Удалить уточнения по ID"), so an agent immediately knows this deletes ad extensions identified by ID. It does not name or contrast with siblings such as list_ad_extensions, add_ad_extensions, delete_sitelinks, or delete_vcards, so differentiation is left to the tool name alone.

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 alternatives: nothing says when deletion is appropriate, whether the extension must first be unlinked, or that sibling delete tools (delete_sitelinks, delete_vcards) target different resource types. The only usage signal is the warning that the operation is irreversible.

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