Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

Обновить кампанию

update_campaign
Idempotent

Modify a Yandex.Direct campaign’s name, daily budget, UTM tracking, Metrica counters, attribution model, or serving status to revise settings and control ad delivery.

Instructions

Обновить кампанию: название, бюджет (руб), UTM-разметку, счётчики Метрики, модель атрибуции и/или статус (SUSPEND/RESUME/ARCHIVE/UNARCHIVE). Разметка действует на ссылки всех объявлений кампании. Список счётчиков заменяется целиком.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "update_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoНовое название
statusNoДействие со статусом показов: SUSPEND (остановить), RESUME, ARCHIVE, UNARCHIVE
campaign_idYesID кампании, десятичная строка
counter_idsNoСчётчики Метрики: список заменяет прежний целиком (чтобы добавить, передайте старые и новые), null снимает все. Только для текстово-графической кампании. Директ не проверяет, что счётчик существует и принадлежит аккаунту
daily_budgetNoНовый дневной бюджет в рублях
tracking_paramsNoUTM-разметка, дописывается к ссылкам всех объявлений кампании. Без ведущего «?»: utm_source=yandex&utm_campaign={campaign_id}. Допустимы подстановки Директа в фигурных скобках. null снимает разметку
attribution_modelNoНовая модель атрибуции; только для текстово-графической кампании

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / attribution_model
      Added value: +{
      +  "description": "Новая модель атрибуции; только для текстово-графической кампании",
      +  "enum": [
      +    "AUTO",
      +    "FC",
      +    "FCCD",
      +    "LC",
      +    "LSC",
      +    "LSCCD",
      +    "LYDC",
      +    "LYDCCD"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / counter_ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "description": "ID счётчика Метрики",
      +        "pattern": "^[1-9]\\d*$",
      +        "type": "string"
      +      },
      +      "minItems": 1,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Счётчики Метрики: список заменяет прежний целиком (чтобы добавить, передайте старые и новые), null снимает все. Только для текстово-графической кампании. Директ не проверяет, что счётчик существует и принадлежит аккаунту"
      +}
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      +  "type": "boolean"
      +}
  3. First observedv1.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare non-read-only, idempotent, open-world, so the description carries real weight and delivers: the counter list is replaced wholesale, UTM markup propagates to links of all ads in the campaign, and counters/attribution are restricted to text-graphic campaigns. What it does not disclose is what happens on invalid input or whether partial failures roll back.

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?

One front-loaded sentence names the resource and the editable fields, followed by two short sentences on side effects. Dense but every clause carries information; no filler.

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?

For a 7-parameter mutation tool with no output schema and full schema coverage, the description supplies the main behavioral facts an agent needs (partial-update semantics, field scope limits, side effects). Missing only an explicit routing statement versus the manage_* siblings.

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 schema already explains counters replacement, UTM format, and currency. The description's restatement of budget-currency and wholesale counter replacement adds little beyond the schema, so it sits at the baseline.

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?

The description uses a specific verb and resource ("Обновить кампанию") and enumerates exactly which campaign fields can be changed, so an agent can tell what the tool touches. It does not, however, distinguish itself from the sibling manage_campaigns, which plausibly overlaps on status changes.

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?

"и/или" implies a partial-update contract (only supplied fields are modified), which is genuine usage guidance, and the status enum is spelled out. But there is no statement of when to prefer this over manage_campaigns or create_campaign, and no stated preconditions.

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