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

yandex-direct-mcp-plus

by Pavelsiba

Управление динамическими целями

manage_dynamic_targets
Destructive

Create, set bids for, suspend, resume, or delete Yandex.Direct dynamic targets in ad groups, including search and network bids and strategy priorities.

Instructions

Создать, изменить ставки, остановить, возобновить или удалить динамические цели.

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": {
      "action": "<action>"
    },
    "name": "manage_dynamic_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidsNoНовые ставки и приоритеты; обязателен при action=set_bids
actionYesЧто сделать: add, set_bids, suspend, resume или delete (необратимо)
targetsNoЦели для добавления; обязателен при action=add
dynamic_target_idsNoЦели для suspend, resume или delete

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 readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description adds no behavior beyond the enum: it does not repeat that delete is irreversible, does not say whether operations are batched/atomic, and gives no rate-limit or permission context. Only the schema's action parameter carries the irreversibility warning.

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?

A single short sentence with no wasted words and the resource leading. It is, however, so terse that it is close to a restatement of the name and action enum rather than an informative summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, multi-action, batch-capable tool (up to 10,000 IDs / 1,000 targets) with no output schema, yet the description says nothing about result reporting, partial-failure behavior, or per-action prerequisites. For a tool of this complexity the one-line description leaves meaningful gaps.

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%, including the conditional requirements (bids obligatory for set_bids, targets for add, dynamic_target_ids for suspend/resume/delete) and bid semantics ('0 — снять ставку'). The description adds nothing about parameters, so the baseline 3 is appropriate.

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 sentence names a specific resource (динамические цели) and enumerates the operations (создать, изменить ставки, остановить, возобновить, удалить), so an agent can tell it is a mutation tool rather than a reader like list_dynamic_targets. It stops short of explicitly differentiating itself from that sibling by name.

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 when-to-use guidance: nothing says to use list_dynamic_targets for reading, nor what preconditions (campaign/ad group context, existing target IDs) are needed for each operation. The action list is simply mirrored from the enum, so the agent must infer selection logic from the schema alone.

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