Skip to main content
Glama
Sign In
yandex-api-mcp

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.update_ads

Update existing ads in Yandex Direct by supplying ad objects with required IDs, optionally overriding account or client login for multi-project agency calls.

Instructions

Update ads in Yandex Direct.

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": {
      "items": "<items>"
    },
    "name": "direct.update_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesAd objects to update (must include Id).
paramsNoRaw Direct params override (advanced).
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
direct_client_loginNoOverride Direct Client-Login for this call (agency multi-project support).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether updates are partial or full-object replacement, not whether they are reversible, not what permissions or account context are needed, and not what the response contains. For a mutation tool operating on a nested items array, this is a severe gap.

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

Conciseness3/5

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

The single sentence is front-loaded and wastes no words, but its brevity stems from under-specification rather than efficiency. It is appropriately sized only in the sense that there is nothing superfluous.

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 mutation tool with a nested object array, no annotations, and no output schema, the description is far too thin. An agent lacks guidance on idempotency, partial-update semantics, multi-account routing, and expected results, all of which it must infer from the schema alone.

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 baseline of 3 applies: the schema already explains items (must include Id), params override, account_id, and direct_client_login. The description adds no additional parameter meaning beyond what the schema documents.

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

Purpose3/5

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

"Update ads in Yandex Direct" names a specific verb and resource, so the basic action is clear. However, it does nothing to distinguish this low-level Direct API tool from sibling high-level helpers like direct.hf.update_ads_text_bulk or direct.hf.moderate_ads, leaving the agent to guess which update path applies.

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, what prerequisites exist (account_id / client login requirements), or which sibling to prefer for ad edits. Usage is only implied by the name.

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