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

yandex-direct-mcp-plus

by Pavelsiba

Создать группу

create_ad_group

Creates an ad group in a Yandex.Direct campaign with regional targeting. Specify the campaign ID, group name, and region codes from get_regions to control where ads are shown.

Instructions

Создать группу объявлений в кампании с таргетингом по регионам (см. get_regions).

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": "<name>",
      "region_ids": "<region_ids>"
    },
    "name": "create_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНазвание группы
region_idsYesРегионы показа, коды из get_regions: ["225"] — Россия, ["225","-213"] — Россия кроме Москвы, ["0"] — все регионы. Минус-регионы нельзя сочетать с 0 и нельзя отправлять одни, без обычного региона
campaign_idYesID кампании, в которой создаётся группа

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
    • 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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, externally visible operation. The description adds almost nothing beyond that: it does not say what defaults are applied, what identifiers come back, whether the same name can be reused, or what happens on invalid region combinations. For a create tool with only two annotations, this is a thin behavioral profile.

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 short sentence with the action and the targeting scope front-loaded, and no filler. It is efficient, though the brevity leaves the definition doing little explanatory work.

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?

With three required params, no output schema and no nesting, the tool is simple enough that a terse description is defensible, and the schema covers all inputs. Still missing is any statement of what the call returns (presumably a group ID) or what failure conditions look like, which an agent would want for a create operation.

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 documents name, region_ids (with negative-region rules and examples) and campaign_id. The description repeats the region-targeting concept and points at get_regions, but adds no syntax, format or validation detail beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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: create an ad group, inside a campaign, with region targeting. That is concrete enough to separate it from list_ad_groups, update_ad_group and delete_ad_groups. It does not explicitly contrast itself with update_ad_group, so it stops short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(см. get_regions)' gives a real prerequisite: region codes must come from get_regions before calling this tool. Nothing is said about when to prefer update_ad_group over creating a new group, or about prerequisites such as the parent campaign needing to exist, so usage is only implied.

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