Skip to main content
Glama
OlegRadinuk

Yandex Direct MCP Server

by OlegRadinuk

update_ads

Update Yandex Direct text ads: modify title, headline, body, URL, or display path. Approved ads revert to draft and need re-moderation. Use confirm=false for dry-run preview.

Instructions

Update text ads (title, text, URL, etc.).

Note: Updating an approved ad resets it to DRAFT — it must be re-moderated.

Args: ads: List of objects with Id + fields to change: - Id (int): ad ID (required) - TextAd (dict, optional): fields to update: - Title (str): new headline (max 35 chars) - Title2 (str): new second headline (max 30 chars) - Text (str): new body (max 81 chars) - Href (str): new destination URL - DisplayUrlPath (str): display path after domain (max 20 chars)

confirm: True to execute; False returns dry-run plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adsYes
confirmNo
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: resetting approved ads to DRAFT, the need for re-moderation, and the dry-run mode when confirm=False. This provides essential transparency for safety and decision-making.

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?

The description is well-organized with a note and a clear argument breakdown. It is slightly lengthy due to the inlined parameter docs, but every sentence adds necessary information given the sparse schema.

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?

Given no annotations and no output schema, the description covers the purpose, side effects, and parameter details adequately. It does not describe return values or error states, but the core functional context is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the tool description exhaustively details each parameter, including nested fields with character limits and the confirm parameter's purpose. This adds substantial value beyond the minimal schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Update text ads (title, text, URL, etc.)', specifying the exact resource and action. It distinguishes from siblings like delete_ads, add_ads, and moderate_ads by focusing on updating existing ads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a critical note about updating an approved ad resetting it to DRAFT and requiring re-moderation, which guides when to use the tool. However, it does not explicitly compare to alternatives or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OlegRadinuk/yandex-direct-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server