Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Управление ключевыми словами

manage_keywords
Destructive

Suspend, resume, or delete Yandex.Direct keywords by ID. Set the action parameter to pause or restart bidding, or remove keywords permanently; preview changes first with dry_run.

Instructions

Действие над ключевыми фразами: suspend/resume/delete. ⚠️ delete необратимо.

Input Schema

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

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
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds the useful '⚠️ delete is irreversible' warning, but says nothing about the dry_run preview path or bulk/atomicity behavior, which would be valuable for a destructive batch operation.

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?

Extremely front-loaded single sentence: resource, operations, then the irreversibility warning. Nothing wasted, though it is arguably under-specified rather than merely concise.

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 destructive 3-param mutation with no output schema, the description covers the operations and the irreversible-delete caveat but omits the dry_run safety valve and any indication of scope or auth requirements. Adequate but with 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 the schema already documents keyword_ids, action enum and dry_run semantics. The description merely restates the action values and does not add format, ID-source or dry_run guidance beyond the schema baseline.

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 resource (keywords) plus the three concrete operations (suspend/resume/delete), which is far more than a tautology. It does not, however, distinguish itself from near-neighbors like update_keywords, set_keyword_bids or add_keywords, so an agent must infer it is the state-change tool.

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 or when-not-to-use guidance, and no alternatives named. The reader must infer from the verb list alone that this is for lifecycle state changes rather than edits or lots of other keyword tools in the sibling set.

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