Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

set_audience_targets
Destructive

Manage audience targeting conditions in Yandex Direct: add, suspend, resume, delete, or update bids and priorities for retargeting and interest targets.

Instructions

Добавить, остановить, возобновить, удалить аудиторные цели или изменить их ставки.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidsNoНовые ставки и приоритеты; обязателен при action=set_bids
actionYesЧто сделать: add, set_bids, suspend, resume или delete (необратимо)
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
targetsNoУсловия для добавления; обязателен при action=add
audience_target_idsNoУсловия для suspend, resume или delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv1.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds little beyond restating the operations; it omits useful behavioral context such as the irreversibility of delete and the existence of dry_run, which the schema alone carries.

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 compact sentence with the core operations front-loaded and no filler. It is efficient, though its brevity contributes to the gaps noted elsewhere.

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-action mutation tool with no output schema, the description is minimally adequate: it lists the operations but does not explain the action-to-payload coupling, the dry_run verification option, or irreversibility. Annotations cover safety, but the workflow guidance remains thin.

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%, so the schema fully documents all five parameters (including action, dry_run, targets and bids). The description adds no parameter-level meaning, so the baseline of 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 description names a specific resource (аудиторные цели) and enumerates the concrete operations (add, stop, resume, delete, change bids), so an agent understands the tool's scope. It does not explicitly distinguish itself from the sibling list_audience_targets, but the write-oriented wording implies it.

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?

There is no explicit when-to-use/when-not guidance, no prerequisites, and no reference to alternatives like list_audience_targets. Usage is only implied by the enumerated action verbs, and the action-to-required-parameter coupling is left entirely to the schema.

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

Deploy Server

Other Tools