Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

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

manage_keywords
Destructive

Suspend, resume, or delete Yandex.Direct keyword phrases by ID to control ad targeting; deletion is irreversible.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword_ids": "<keyword_ids>",
      "action": "<action>"
    },
    "name": "manage_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesДействие: suspend, resume или delete (необратимо)
keyword_idsYesФразы, над которыми выполняется действие

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      +  "type": "boolean"
      +}
  3. 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 openWorldHint=true, so the safety bar is lower. The description adds one genuinely useful clarification — delete is irreversible — which sharpens rather than repeats the annotation. It says nothing about whether suspend/resume affect bids or status, or whether the tool works across campaigns, so the addition is thin.

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?

One sentence, front-loaded, zero filler, with the irreversibility warning placed immediately after the operation list. It is terse to the point of omitting routing context, but no wording 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 two-parameter mutation tool with full schema coverage and destructive annotations, the description covers the essentials. It leaves out scope details an agent could want — whether keyword_ids may span campaigns, expected response, and partial-failure behavior — so it is adequate rather than complete.

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% and the enum is already documented in the action property, so the description only restates the same three values. The bulk action over keyword_ids (single vs many, mixed actions not permitted) is not elaborated beyond the schema.

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 concrete operation set on a concrete resource: "Действие над ключевыми фразами: suspend/resume/delete". An agent can tell this is a state-change tool for existing keywords, but the description does not name the sibling tools (update_keywords, add_keywords, list_keywords) it should be chosen over.

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 beyond the enum. It never distinguishes this from update_keywords or from other delete operations in the sibling list, so the agent must infer routing from the name alone.

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