Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Добавить уточнения

add_callouts

Creates callout texts of up to 25 characters each, with a limit of 1,000 per call. Use them to add ad extensions; edit by deleting and recreating, then link them to ads via the Ads service.

Instructions

Создаёт уточнения, до 25 символов каждое, не более 1000 за вызов. Уточнения неизменяемы — чтобы поменять, нужно удалить и создать заново. Привязка к объявлениям — через сервис Ads.

Input Schema

NameRequiredDescriptionDefault
textsYesТексты уточнений, до 25 символов каждый, не более 1000 за вызов.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.11.0
    • changedInput schema / properties / texts / description
      Previous value: -"Тексты уточнений, до 25 символов каждый."New value: +"Тексты уточнений, до 25 символов каждый, не более 1000 за вызов."
    • addedInput schema / properties / texts / maxItems
      Added value: +1000
  2. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / client_login
      Added value: +{
+  "description": "Логин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.",
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._@-]{0,99}$",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / texts / description
      Previous value: -"Callout texts, up to 25 characters each."New value: +"Тексты уточнений, до 25 символов каждый."
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds substantive behavioral context: the 25/1000 limits, the immutability constraint forcing delete+recreate, and that ads binding happens in a separate Ads service. This is real value beyond the annotations, though it omits what the response contains for the newly created items.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero waste, and the core creation action plus limits are front-loaded before the immutability caveat. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with full annotation coverage and no output schema, the description covers creation semantics, limits, immutability, and cross-service binding. It is nearly complete; the main gap is that it doesn't indicate whether the response returns created callout IDs needed for the Ads-side binding.

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 coverage is 100%, so both parameters (texts, client_login) are already documented in the schema, including the client_login fallback logic. The description repeats the 25/1000 constraint that the schema already encodes, adding no new parameter semantics. 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 states a specific verb+resource ("Создаёт уточнения" = creates callouts) with scope limits (25 chars, 1000/call). It is clear what the tool does, though it doesn't explicitly name the sibling it differs from (get_callouts/delete_callouts are only implied by the immutability note).

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?

It implies usage via the immutability note ("to change, delete and recreate") and the cross-service binding note ("binding to ads — via Ads service"), which is helpful routing context. However, it never explicitly says when to use this vs get_callouts/delete_callouts or what preconditions (a client_login) select a different path.

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