Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

create_ad_group

Add an ad group to a Yandex.Direct campaign with regional targeting using region IDs. Retrieve valid region codes with get_regions before setup.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
+  "type": "boolean"
+}
  2. 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 only give readOnlyHint=false and openWorldHint=true. The description carries the rest of the burden for a mutation tool but says nothing about side effects, permission/auth requirements, rate limits, or what happens on partial failure. It never mentions the dry_run safety path that the schema exposes.

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?

A single front-loaded sentence with no filler; the essential verb+resource+scope comes first. It is terse to the point of omitting useful invocation context, but nothing is wasted.

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 mutation tool with no output schema and thin annotations, the description is only minimally sufficient. The schema fully documents parameters, but the description omits mutation semantics, the dry_run option, and any preconditions an agent would want before writing.

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 baseline is 3. The description only reinforces the region_ids/get_regions link already documented in the schema and adds no syntax, constraint, or interaction detail beyond it.

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?

States a specific verb+resource ('Создать группу объявлений в кампании') and adds a scope qualifier (region targeting). It is identifiable against siblings like create_campaign or create_text_ad, though it doesn't explicitly name a near alternative.

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)' implies you must fetch region codes first, which is usable guidance. However, there is no when-to-use/when-not statement, no mention of required preconditions such as an existing campaign or dry_run for validation.

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

Deploy Server

Other Tools