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

yandex-direct-mcp-plus

by Pavelsiba

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

add_retargeting_list

Creates a retargeting condition in Yandex.Direct from Metrica goals or Yandex Audience segments, combining rules with ALL, ANY, or NONE logic to target ads to the right users.

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": {
      "name": "<name>",
      "rules": "<rules>"
    },
    "name": "add_retargeting_list"
  }
}

Input Schema

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

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 declare readOnlyHint=false and openWorldHint=true, so the agent already knows this is a mutating external call. Beyond that, the description says nothing about persistence of the created list, duplication behavior, irreversibility, or account-level quotas, which matters for a creation tool with no output 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?

One front-loaded sentence with the verb first and no filler or repetition of schema fields. It is efficient, though the terseness leaves little room for the routing cues an agent actually needs.

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 tool has a nested rules structure with ALL/ANY/NONE operators and an external_id list, and the description explains none of that combination logic, while also having no output schema to describe the created object. The fully documented schema covers the mechanics, but the description does not address the complexity of the payload.

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 already explains name, type, rules, operators and external_id, which sets the baseline at 3. The description adds only a high-level hint about sources and introduces "интересы", which maps to no value in the type enum (RETARGETING/AUDIENCE), so it neither clarifies nor fully compensates.

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?

States a specific verb plus resource ("Создать условие ретаргетинга") and names the three data sources it can be built from. An agent can distinguish it from list/update/delete_retargeting_lists, though the description never names those siblings explicitly, and it shifts wording between "список" (title) and "условие" (description).

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?

No statement of when to use this tool rather than update_retargeting_lists or an audience target tool, and no prerequisites or limits (e.g. max lists per account). The only usage signal is implicit in the verb "создать".

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