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

yandex-direct-mcp-plus

by Pavelsiba

Создать уточнения

add_ad_extensions

Adds callout extensions to Yandex.Direct ads by accepting up to 1,000 benefit phrases, each 25 characters or fewer, to clarify offers in ad copy.

Instructions

Создать уточнения (callouts), каждый текст до 25 символов.

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": {
      "callouts": "<callouts>"
    },
    "name": "add_ad_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
calloutsYesТексты уточнений, каждый до 25 символов

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 and openWorldHint=true, so the mutation/remote-API nature is covered structurally. Beyond that, the description adds only the 25-character limit, which is already in the schema, and says nothing about whether callouts are appended or replace existing ones, what the size limit per entity is, or what permissions are required. For a write tool this leaves the real behavioral questions unanswered.

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 constraint front-loaded and no filler. It is efficient, though the brevity borders on under-specification given the mutation semantics.

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?

For a write operation with no output schema, the description should at minimum say what entity the callouts attach to, whether the call is additive, and what a successful result looks like. None of that is present, and the annotations cover only the read/write and world-access dimensions.

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% and there is only one parameter, whose array/string bounds are fully encoded in the schema. The description merely restates the 25-character constraint, adding no new meaning such as whether duplicates are rejected or how array order matters. 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 description names a specific verb and resource — creating callout extensions — and adds the parenthetical '(callouts)' to disambiguate the term 'уточнения' for a non-Russian reader. It is clearly distinguishable from the read/delete siblings (list_ad_extensions, delete_ad_extensions), though it never states what the extensions are attached to (campaign, ad group, or account).

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, no mention of prerequisites (an existing campaign/ad group to attach the callouts to), and no reference to any alternative such as list_ad_extensions or delete_ad_extensions. The agent must infer the workflow entirely from the tool name.

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