Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Создать список ретаргетинга

add_retargeting_list

Creates a Yandex.Direct retargeting condition from Metrica goals, Audience segments, or interests using ALL/ANY/NONE rules, with optional dry-run validation.

Instructions

Создать условие ретаргетинга из целей Метрики, сегментов или интересов.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesНазвание условия ретаргетинга
typeNoRETARGETING — по целям Метрики, AUDIENCE — по сегментам Яндекс.АудиторийRETARGETING
rulesYesПравила условия; между собой они соединяются логическим И
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
descriptionNoОписание условия — видно только в интерфейсе, на показы не влияет

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
+  "type": "boolean"
+}
  2. 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 and openWorldHint=true, so the write/open-world nature is covered. The description adds nothing behavioral: no mention of the dry_run preview path, permissions, or side effects on existing lists. For a mutation tool it leaves the operational profile entirely to the schema.

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 front-loaded sentence with no filler. It is efficiently sized, though its brevity is as much under-specification as conciseness.

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?

The rich schema carries most of the load, but a create-style mutation tool benefits from stating prerequisites and the dry_run preview option, neither of which appears in the description. The definition is adequate but not complete for the operation it performs.

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 detailed enum semantics for type, operator, and membership_life_span, so the baseline is 3. The description only loosely gestures at the type parameter ('целей Метрики, сегментов или интересов') and adds no format or constraint detail beyond the schema.

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 ('условие ретаргетинга'), and names the sources (Метрика goals, segments, interests), which aligns with the sibling set. It does not, however, distinguish itself from the other retargeting siblings (update_retargeting_lists, delete_retargeting_lists), so sibling differentiation is only implicit via the verb.

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?

It says what the tool does but gives no when-to-use guidance, no prerequisites (e.g. account context), and never mentions alternatives such as update_retargeting_lists or set_audience_targets. An agent must infer routing from the name alone.

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