Skip to main content
Glama
Yandex Direct MCP

Yandex Direct MCP

Обновить текстовое объявление

update_text_ad
Idempotent

Updates the title, text, or landing page of a Yandex Direct text ad; editing an active ad sends it back for moderation.

Instructions

Обновляет заголовок, текст или посадочную страницу текстового объявления (ads/update). Правка активного объявления отправляет его на повторную модерацию.

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": {
      "id": "<id>"
    },
    "name": "update_text_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId объявления, которое нужно обновить. Длинный id (приходит в ответах строкой) передавать строкой как есть.
hrefNoНовый URL посадочной страницы.
textNoНовый текст объявления, до 81 символа.
titleNoНовый заголовок (Title 1), до 56 символов.
title2NoНовый второй заголовок (Title 2), до 30 символов.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.14.0
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^\\d+$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / id / description
      Previous value: -"Id объявления, которое нужно обновить."New value: +"Id объявления, которое нужно обновить. Длинный id (приходит в ответах строкой) передавать строкой как есть."
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  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. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / href / description
      Previous value: -"New landing page URL."New value: +"Новый URL посадочной страницы."
    • changedInput schema / properties / id / description
      Previous value: -"Ad id to update."New value: +"Id объявления, которое нужно обновить."
    • changedInput schema / properties / text / description
      Previous value: -"New body text, up to 81 characters."New value: +"Новый текст объявления, до 81 символа."
    • changedInput schema / properties / title / description
      Previous value: -"New Title (Title 1), up to 56 characters."New value: +"Новый заголовок (Title 1), до 56 символов."
    • changedInput schema / properties / title2 / description
      Previous value: -"New second title (Title 2), up to 30 characters."New value: +"Новый второй заголовок (Title 2), до 30 символов."
  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?

The annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower, and the description still adds a genuinely non-obvious trait: editing an active ad resubmits it for moderation. It does not say whether fields are partially updated, whether the ad is paused during review, or what the response contains.

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?

Two short sentences with zero filler: the operation and endpoint come first, the moderation consequence second. Every clause 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 six-parameter mutation tool with a fully documented schema, no output schema, and annotations covering the safety profile, the description supplies the one behavioral fact an agent most needs (moderation re-review). It could go further on partial-update semantics and on the title2 field it omits.

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 each parameter (including the id string/integer form, length caps, and client_login fallback) is already fully documented in the schema. The description merely restates three field names and adds no syntax or format meaning beyond that, making the baseline 3 correct.

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 ('Обновляет заголовок, текст или посадочную страницу текстового объявления') and even cites the backing endpoint (ads/update), so the operation is unambiguous. It stops short of 5 because it enumerates only three of the four editable fields (title2 is absent) and never explicitly contrasts itself with create_text_ad or the other update_* siblings.

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?

Usage is only implied: 'updates' an existing ad presupposes an existing ad id, but the description never states prerequisites or when to prefer create_text_ad over this tool. The moderation sentence is a side-effect warning rather than guidance on when to call it.

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