Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

update_text_ad
Idempotent

Update a Yandex.Direct text ad's title, text, and destination link, then submit the revised ad for moderation.

Instructions

Обновить текстовое объявление: заголовок, текст, ссылка. Изменённое объявление уходит на модерацию.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hrefNoНовая ссылка на сайт
textNoНовый текст объявления
ad_idYesID обновляемого объявления
titleNoНовый заголовок
title2NoНовый второй заголовок
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.

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

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and idempotentHint=true, but the description adds a genuinely useful consequence: the edited ad is sent back to moderation ("уходит на модерацию"), which explains a delayed/non-immediate effect. It does not mention permission requirements or what happens to fields left unset.

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, zero filler. The action and affected fields come first, and the moderation consequence is a targeted second sentence that 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 schema coverage, annotations, and no output schema, the description covers intent and the moderation side effect adequately. Missing are prerequisites and any note that modified ads may need re-approval before serving, but nothing critical blocks a correct call.

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 documents all six parameters, including dry_run's preview semantics and the maxLength constraints. The description's partial field list (title, text, link) adds little and even omits title2, so the 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 ("Обновить текстовое объявление") and enumerates the mutable fields, so an agent knows exactly what the tool touches. It does not differentiate itself from ambiguous siblings such as manage_ads or moderate_ads, and it omits title2, which the schema exposes.

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 statement of when to use this tool versus create_text_ad, manage_ads, or moderate_ads, nor any precondition (ad must exist, must belong to the account, editing limits after moderation). The agent is left to infer everything about context.

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