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

yandex-direct-mcp-plus

by Pavelsiba

Добавить ключевые слова

add_keywords

Adds keyword phrases to a specified Yandex.Direct ad group so you can build or expand campaign targeting directly from your MCP client.

Instructions

Добавить ключевые фразы в группу объявлений.

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": {
      "ad_group_id": "<ad_group_id>",
      "keywords": "<keywords>"
    },
    "name": "add_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesКлючевые фразы; минус-слова внутри фразы записываются через дефис
ad_group_idYesID группы, в которую добавляются фразы

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

C2.6/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false and openWorldHint=true, so the write/external-effect profile is covered. Beyond that the description adds nothing: it does not say whether duplicates are skipped or rejected, whether keywords enter a moderation state, whether the operation is additive-only or idempotent, or what the response contains.

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?

A single short sentence with no filler, and the action and destination are front-loaded. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere rather than through disciplined editing.

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?

This is a mutating, open-world tool with no output schema and a large family of keyword-related siblings. With annotations covering only the safety flags, the description should carry the load on effects, limits and alternatives, and it does none of that.

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 both parameters (ad_group_id, keywords) are documented in the schema, including the hyphen convention for minus-words. The description adds no meaning beyond that, 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 sentence names a verb (add) and a resource (keywords into an ad group), so the basic action is recoverable. But it is nearly a restatement of the title and does nothing to separate it from closely overlapping siblings such as update_keywords, manage_keywords, list_keywords and set_keyword_bids.

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 mention of prerequisites (campaign/ad group must exist, permissions, moderation), and no routing to alternatives. An agent cannot tell from the description why it should pick add_keywords over update_keywords or manage_keywords for a given request.

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