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

yandex-direct-mcp-plus

by Pavelsiba

Управление общими минус-фразами

manage_negative_keyword_shared_sets
Destructive

Create, update, or delete account-level shared negative keyword sets in Yandex Direct, including set names and full keyword lists, to centralize exclusions across campaigns.

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": {
      "action": "<action>"
    },
    "name": "manage_negative_keyword_shared_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать с наборами: add, update или delete (необратимо)
set_idsNoНаборы для удаления; обязателен при action=delete
add_setsNoНаборы для создания; обязателен при action=add
update_setsNoНаборы для изменения; обязателен при action=update

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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, and the description merely echoes 'delete' without adding anything an agent could not infer. It omits operationally relevant behavior: what happens to sets currently linked to campaigns when deleted, whether updates are atomic across the up-to-30 batch, and any rate or quota limits. With annotations covering the safety profile, this is a case where the description adds no context beyond structured data.

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 front-loaded sentence with no filler — appropriately sized. It is not padded, but it is also so terse that the space it saves is space an agent needed for action routing.

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?

With 4 well-documented parameters, full schema coverage, no output schema, and annotations that already flag destructiveness, the definition is minimally sufficient to call the tool. It is incomplete for the multi-mode (add/update/delete) shape of the tool, where the caller most needs guidance on which mode to select and what the irreversible consequences are.

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 schema itself already explains action-dependent requirements ('обязателен при action=delete'), the destructive nature of delete, and that update replaces the keyword list wholesale. The description contributes nothing beyond that, so the 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?

The description gives a specific verb set (create/modify/delete) plus a specific resource (account-level shared negative keyword sets), which is enough to distinguish it from read-only siblings such as list_negative_keyword_shared_sets. It does not, however, distinguish it from link_negative_keyword_sets or set_campaign_negative_keywords, which touch overlapping concepts.

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 at all: nothing says when to prefer this tool over link_negative_keyword_sets (attaching an existing set) or set_campaign_negative_keywords (campaign-scoped negatives). The one required 'action' parameter is the natural place to hang routing guidance, but the description says nothing about it.

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