Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Управление кампаниями

manage_campaigns
Destructive

Start, stop, archive, unarchive, or delete Yandex.Direct campaigns. Delete is irreversible and blocked for campaigns with accumulated stats; archive those instead.

Instructions

Запустить, остановить, архивировать, разархивировать или удалить кампании. ⚠️ delete необратимо и недоступен кампании с накопленной статистикой — такую только архивировать.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesДействие: suspend, resume, archive, unarchive или delete (необратимо)
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
campaign_idsYesID кампаний, над которыми выполняется действие

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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the warning is partly pre-covered, but the description goes beyond them: it pinpoints that delete is the irreversible action and that campaigns with accumulated statistics cannot be deleted at all. This is genuine operational context not derivable from the annotation alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences: the action list first, then the destructive-constraint warning with a warning glyph. Zero filler and the riskiest information is deferred only slightly and clearly marked.

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 3-parameter mutation tool with full schema coverage, annotations, and no output schema, the definition covers purpose and the key destructive constraint. It does not mention dry_run semantics or batch size limits, which are left entirely to the schema, but nothing critical is missing.

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 action enum, campaign_ids pattern/limits and dry_run are all documented in the schema. The description only re-states that delete is irreversible, adding no new parameter detail; baseline 3 applies.

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 set (suspend/resume/archive/unarchive/delete) applied to the resource 'кампании', so the agent knows exactly which operations are covered. It does not differentiate itself from siblings such as update_campaign or create_campaign, though the enumerated action list makes overlap unlikely.

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 description implicitly tells the agent to use archive instead of delete when a campaign has accumulated statistics — a real routing rule. However it gives no guidance on when to pick this bulk-action tool over update_campaign, list_campaigns, or get_campaign, and no preconditions for the other actions.

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