Skip to main content
Glama
Yandex Direct MCP

Yandex Direct MCP

Создать группу объявлений

create_ad_group

Creates an ad group within a Yandex Direct campaign using a name, parent campaign ID, and target region IDs.

Instructions

Создаёт группу объявлений в кампании с заданными регионами показа. Запрос идёт в 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": {
      "name": "<name>",
      "campaignId": "<campaignId>",
      "regionIds": "<regionIds>"
    },
    "name": "create_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНазвание группы объявлений.
regionIdsYesId регионов показа, например [225] — Россия.
campaignIdYesId родительской кампании.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / campaignId / description
      Previous value: -"Parent campaign id."New value: +"Id родительской кампании."
    • changedInput schema / properties / name / description
      Previous value: -"Ad group name."New value: +"Название группы объявлений."
    • changedInput schema / properties / regionIds / description
      Previous value: -"Target geo region ids, e.g. [225] for Russia."New value: +"Id регионов показа, например [225] — Россия."
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely non-obvious behavioral fact — that it targets API v501, and v5 in sandbox — which matters for anyone reproducing calls across environments. It does not disclose what an agent gets back (no created group ID), what happens if the campaign is closed, or whether name collisions are rejected, so it adds value but not rich operational context.

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 with no padding; the core operation is front-loaded before the API-version note. The version sentence is arguably peripheral to tool selection, but it is not redundant given the rest of the text.

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?

There is no output schema, so nothing else tells the agent what a successful creation returns, and the description does not fill that gap. Given a mutation tool with four fully documented parameters and complete annotations, the definition is callable as-is but leaves error behavior and return shape unstated.

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 all four parameters, including the client_login fallback chain to YANDEX_DIRECT_LOGIN, are already documented in the schema. The description's mention of "заданными регионами показа" merely echoes the regionIds parameter and adds no format or constraint detail beyond it. Baseline 3 is correct when the schema carries the semantics.

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 states a specific verb and resource ("Создаёт группу объявлений в кампании") and adds the required scoping dimension (display regions). It does not name a sibling such as update_ad_group or list_ad_groups, so the agent must infer the create-vs-update boundary from the name alone, which keeps it below a 5.

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: nothing says this is for new groups only, nothing points to update_ad_group for existing groups or list_ad_groups for discovery, and no prerequisites (e.g. that a valid campaignId must already exist) are stated. The purpose sentence implies creation, but selection against alternatives is left entirely to inference.

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