Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Отправить объявления на модерацию

moderate_ads
Idempotent

Submit selected Yandex.Direct ads for moderation by ID. Use dry_run to validate parameters and preview request bodies without changing data.

Instructions

Отправить выбранные объявления на модерацию.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idsYesОбъявления, отправляемые на модерацию
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.

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

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=true, so the mutation and idempotency profile is covered without the description. The description adds nothing beyond that: it does not say what moderation triggers, whether it is reversible, what authorization or account state is required, or how partial failures across a batch are handled.

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

Conciseness2/5

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

It is a single short sentence, but its brevity comes from duplication of the title rather than editing — it earns almost nothing on its own. There is no front-loaded constraint or behavioral detail to justify the minimalism.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a bulk mutation tool accepting up to 10,000 IDs with no output schema, the description should at least explain what moderation means operationally and how results are reported. Neither is present, leaving a significant gap for an agent deciding whether to invoke it.

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 coverage is 100%, so both ad_ids and dry_run are fully documented in the schema, including the 10,000-item cap and the dry-run semantics. The description contributes no additional parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a clear verb+resource ('отправить объявления на модерацию'), but it is essentially a verbatim restatement of the title and adds no scope or differentiation. An agent cannot tell from the text how this relates to siblings like manage_ads or update_text_ad, which also touch individual 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as manage_ads. The 'выбранные' (selected) wording lightly implies the caller must first pick ad IDs, but nothing routes the agent between this tool and its siblings.

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