Skip to main content
Glama
askads

Yandex Direct MCP

Update ad group

update_ad_group
Idempotent

Update an ad group's name, target regions, and negative keywords to refine campaign targeting.

Instructions

Updates an ad group's name and/or target regions (adgroups/update).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAd group id to update.
nameNoNew ad group name.
regionIdsNoNew target geo region ids.
negativeKeywordsNoReplace the ad group's negative keywords; pass an empty array to clear them.
Behavior2/5

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

Annotations already signal non-destructive, idempotent, open-world. Description adds no behavioral context beyond listing updatable fields (missing negativeKeywords). Could mention replacement behavior or idempotency.

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?

Single sentence, no fluff, but includes redundant endpoint name '(adgroups/update)'. Could be more concise by listing all parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple update tool with decent annotations. However, missing negativeKeywords from description and no output schema details make it only partially complete.

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 has 100% coverage, so baseline 3. Description partially covers parameters but omits negativeKeywords, reducing added value. Baseline maintained.

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?

Clearly states it updates ad groups and specifies fields (name, target regions), but omits negativeKeywords from description. Distinguishes from create/delete/list 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?

No explicit when-to-use or alternatives provided. Implied by tool name and sibling list, but lacks guidance on when to prefer this over update_campaign or other tools.

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/askads/mcp-yandex-direct'

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