Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba

Управление объявлениями

manage_ads
Destructive

Suspend, resume, archive, unarchive, moderate, or delete Yandex.Direct ads by ID. Deleting is irreversible, so verify IDs before running bulk actions.

Instructions

Действие над объявлениями: suspend/resume/archive/unarchive/moderate/delete. ⚠️ delete необратимо.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesДействие: suspend, resume, archive, unarchive, moderate или delete (необратимо)
ad_idsYesОбъявления, над которыми выполняется действие

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the pinpointed fact that specifically 'delete' is irreversible (⚠️ delete необратимо), which is genuinely additive over the blanket destructive flag. It still omits permission requirements and what suspend/archive do to live serving, but clears the lowered bar set by annotations.

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 compact sentences with the action set front-loaded and the destructive caveat attached directly to the dangerous action. No filler; every clause earns its place.

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?

Adequate for a 2-param mutation tool with full schema coverage and safety annotations, and no output schema to explain. But for a six-action destructive tool it omits what non-delete actions actually change and any preconditions, leaving clear gaps.

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 both 'action' (enum) and 'ad_ids' are fully documented in the schema, including the irreversibility note on delete. The description only restates the enum values already present, adding no syntax or format detail beyond the schema, so 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?

States a clear verb+resource ('Действие над объявлениями') and enumerates the exact action set, so the agent knows precisely what the tool does. However, it offers no differentiation from the sibling 'moderate_ads', which appears to overlap with the 'moderate' action listed here, nor from delete_ad_groups/list_ads.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is not told when to pick manage_ads versus moderate_ads or the create/update_text_ad siblings, despite the overlap.

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