Skip to main content
Glama
Yandex Direct MCP

Yandex Direct MCP

Обновить группу объявлений

update_ad_group
Idempotent

Update an ad group's name, display regions, or negative keywords in Yandex Direct to revise targeting settings for an existing group.

Instructions

Обновляет название и/или регионы показа группы объявлений (adgroups/update). Запрос идёт в API v501, в песочнице — в v5.

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": {
      "id": "<id>"
    },
    "name": "update_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId группы, которую нужно обновить.
nameNoНовое название группы.
regionIdsNoНовые id регионов показа.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.
negativeKeywordsNoЗаменяет минус-фразы группы; пустой массив очищает их. Чтобы дописать или убрать отдельные фразы, не затирая список, — update_negative_keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.1
    • changedInput schema / properties / negativeKeywords / description
      Previous value: -"Заменяет минус-фразы группы; пустой массив очищает их."New value: +"Заменяет минус-фразы группы; пустой массив очищает их. Чтобы дописать или убрать отдельные фразы, не затирая список, — update_negative_keywords."
  2. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / client_login
      Added value: +{
      +  "description": "Логин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.",
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._@-]{0,99}$",
      +  "type": "string"
      +}
  3. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / id / description
      Previous value: -"Ad group id to update."New value: +"Id группы, которую нужно обновить."
    • changedInput schema / properties / name / description
      Previous value: -"New ad group name."New value: +"Новое название группы."
    • changedInput schema / properties / negativeKeywords / description
      Previous value: -"Replace the ad group's negative keywords; pass an empty array to clear them."New value: +"Заменяет минус-фразы группы; пустой массив очищает их."
    • changedInput schema / properties / regionIds / description
      Previous value: -"New target geo region ids."New value: +"Новые id регионов показа."
  4. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true and openWorld=true, so the safety profile is covered. The description adds genuinely new operational context — the request targets API v501 and v5 in the sandbox — but does not disclose partial-update semantics, that omitted fields are left untouched, or what the call returns.

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?

Two short sentences, front-loaded with what is updated, followed by the endpoint and API-version note; nothing is padded. The second sentence is slightly tangential but does carry environment-specific behavior an agent may need.

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?

For a 5-parameter mutation with full schema coverage and annotations, most of the burden is carried by structured fields. Gaps remain: the description omits the negativeKeywords replacement behavior from its own scope statement and, with no output schema, says nothing about the response or whether partial updates are atomic.

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%, including the note that an empty negativeKeywords array clears the list and a redirect to update_negative_keywords, so the baseline is 3. The description only restates that name and regionIds are optional/updatable and adds no syntax, constraints, or ID-source detail beyond the schema.

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?

Names a specific verb and resource ("Обновляет название и/или регионы показа группы объявлений") and pins the endpoint (adgroups/update), so it is distinguishable from update_campaign and update_text_ad. The scope statement is incomplete, however: the schema also accepts negativeKeywords, which silently replaces the group's minus-phrases, yet the description presents the tool as name/region-only.

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?

The "и/или" wording implies a partial update where any subset of fields may be supplied, which is real usage context. There is no explicit when-to-use versus when-not guidance (e.g., pointing at update_negative_keywords for additive edits), and no prerequisites such as required permissions or that the group must already exist.

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