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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.update_adgroups

Update existing ad groups in Yandex Direct by passing ad group objects that include their IDs and revised fields.

Instructions

Update ad groups 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_adgroups"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesAd group 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.5/5.0
Behavior2/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 almost nothing: not whether the update is partial or full-replace, what happens to unspecified fields, whether it is destructive, what batch limits apply, or what auth/account context is needed. Only the word 'Update' signals a mutation at all.

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?

A single short sentence is front-loaded and waste-free, but at this level it reads as under-specification rather than conciseness given a 4-parameter mutation tool with nested objects and no annotations. It is terse but not informative.

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 no annotations, no output schema, and nested object parameters, the description is insufficient: it omits update semantics, required fields beyond Id, account/agency scoping behavior, and any failure or partial-success behavior. The gaps are structural, not cosmetic.

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% (each of the 4 parameters has its own description, including the nested 'items' array requiring Id and the account_id/direct_client_login fields), so the schema does the heavy lifting. The description adds no parameter meaning beyond that baseline.

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?

The description states a verb (Update) and resource (ad groups) plus the platform (Yandex Direct), but that content is almost entirely a restatement of the tool name 'direct.update_adgroups'. It gives no indication of what fields can be updated or how it differs from siblings such as direct.hf.update_adgroup_geo, direct.hf.set_adgroup_negative_keywords, or direct.create_adgroups.

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 when-to-use guidance, no prerequisites, and no named alternatives, despite a crowded sibling set that includes granular ad-group mutation tools. An agent must infer from the name alone that this is the generic bulk-update path versus the specialized hf.* variants.

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