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

yandex-direct-mcp-plus

by Pavelsiba

Управление объявлениями

manage_ads
Destructive

Suspend, resume, archive, unarchive, moderate, or delete Yandex.Direct ads by ID; deletion is irreversible.

Instructions

Действие над объявлениями: suspend/resume/archive/unarchive/moderate/delete. ⚠️ delete необратимо.

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_ids": "<ad_ids>",
      "action": "<action>"
    },
    "name": "manage_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesДействие: suspend, resume, archive, unarchive, moderate или delete (необратимо)
ad_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the destructive profile is known to the agent without the prose. The description's warning that delete is irreversible adds a concrete detail beyond the boolean, but it merely restates what the schema enum description also says, and it says nothing about multi-ad behavior, partial failure, or moderation semantics.

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 clauses with zero filler: the operation set is front-loaded and the destructive warning is placed last with an explicit warning marker. It is a fragment rather than a full sentence, but nothing is redundant.

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?

With only two required parameters, full schema coverage and a complete annotation set, the definition is adequate for correct invocation. However, for a destructive bulk mutation it omits whether ad_ids are processed atomically, what happens on partial failure, and how 'moderate' relates to the dedicated moderate_ads tool.

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%: both parameters carry descriptions, the action enum is fully enumerated with the irreversibility note, and ad_ids specifies item pattern and minItems. The description adds no meaning beyond the schema — it repeats the action list verbatim. Baseline 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 names a concrete resource (объявления) and enumerates the exact operations available (suspend/resume/archive/unarchive/moderate/delete), so an agent can map an intent to an action directly. It does not distinguish itself from the sibling moderate_ads tool, which overlaps with the 'moderate' action in this same enum — a real ambiguity left unaddressed.

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 explicit when-to-use / when-not-to-use guidance and no mention of the alternative path via moderate_ads for the 'moderate' action, nor of list_ads as the prerequisite for obtaining ad_ids. Usage is only implied by the enum list itself.

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