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

yandex-direct-mcp-plus

by Pavelsiba

Управление аудиторными целями

set_audience_targets
Destructive

Manage Yandex.Direct audience targets by adding, suspending, resuming, or deleting targeting conditions and updating bids or priorities for campaigns and ad groups.

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": "set_audience_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidsNoНовые ставки и приоритеты; обязателен при action=set_bids
actionYesЧто сделать: add, set_bids, suspend, resume или delete (необратимо)
targetsNoУсловия для добавления; обязателен при action=add
audience_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. Changed2 schema fields changedv1.7.0
    • changedInput schema / properties / bids / items / properties / context_bid / description
      Previous value: -"Ставка в сетях в рублях; 0 — снять ста��ку"New value: +"Ставка в сетях в рублях; 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 and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not mention that delete is irreversible (that fact lives only in the schema), nor permission requirements, limits, or whether changes are batched atomically.

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?

One compact sentence with the actions front-loaded and zero filler. It is as short as it can be, though the brevity costs it structure such as a mapping of action to required parameters.

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 destructive, multi-mode mutation tool with an action-discriminated schema, the description is minimally sufficient because the schema documents the per-action requirements and irreversibility. It still leaves an agent to infer mode selection and caution around delete from the schema rather than the prose.

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 per-action requirements ('обязателен при action=add') and the 'delete (необратимо)' note, so the schema carries the parameter burden. The description adds no additional meaning about targets vs bids vs audience_target_ids; 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 specific resource (аудиторные цели) and enumerates concrete verbs matching the action enum: add, suspend, resume, delete, change bids. It is clear what the tool does, but it is not differentiated from siblings such as list_audience_targets, set_bid_adjustments, or add_retargeting_lists.

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 choose this tool over list_audience_targets / manage_dynamic_targets / add_bid_adjustments, and no prerequisites or exclusions. The only implied usage comes from the verb list, which merely restates the action enum.

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