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

yandex-direct-mcp-plus

by Pavelsiba

Привязать общие минус-фразы

link_negative_keyword_sets
Idempotent

Replace shared negative keyword set bindings for campaigns or ad groups; use an empty set_ids list to clear all existing bindings.

Instructions

Заменить привязки общих наборов минус-фраз у кампаний и/или групп объявлений. Привязка к кампании действует на все её группы. Пустой set_ids очищает привязки.

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": {
      "set_ids": "<set_ids>"
    },
    "name": "link_negative_keyword_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
set_idsYesПолный новый список наборов объекта — прежние привязки затираются. Пустой массив снимает все
ad_group_idsNoГруппы, которым назначаются наборы
campaign_idsNoКампании, которым назначаются наборы. Привязка на уровне кампании действует на все её группы. Тип кампании сервер читает сам — это дополнительный вызов API; общие наборы поддерживают TEXT_CAMPAIGN, DYNAMIC_TEXT_CAMPAIGN, MOBILE_APP_CAMPAIGN и UNIFIED_CAMPAIGN

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=true, so the bar is lower. The description still adds substantive behavior: this is a destructive overwrite of prior bindings, campaign-level bindings cascade to all ad groups, and an empty array removes all bindings — all consistent with idempotentHint. It says nothing about required permissions or failure modes, so not a 5.

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?

Three short sentences, front-loaded with the replace operation and followed by the two behavioral facts an agent most needs (cascade and clearing). The third sentence duplicates a facet already spelled out in the schema, so it is not maximally economical, but nothing is bloated.

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

Completeness4/5

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

For a 3-parameter mutation tool with no output schema and 100% schema coverage, the description supplies the essential semantics: overwrite behavior, cascade to ad groups, and the clearing case. Remaining gaps — how campaign_ids and ad_group_ids interact when both are supplied, and whether the response enumerates affected bindings — are modest.

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 baseline is 3. The description's mentions of empty set_ids clearing and campaign-level propagation largely restate the parameter descriptions already present in the schema ("Пустой массив снимает все", "Привязка на уровне кампании действует на все её группы"), adding little new meaning beyond them.

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 states a specific verb ("Заменить" / replace) applied to a specific resource (bindings of shared negative-keyword sets) with explicit scope (campaigns and/or ad groups). It also signals replace-not-append semantics, which differentiates it from additive siblings. It does not explicitly name the sibling (manage_negative_keyword_shared_sets / set_campaign_negative_keywords) to route against, so 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied: the tool replaces existing bindings, and an empty set_ids clears them, which tells an agent when clearing is appropriate. However, it never states when to prefer this tool over set_campaign_negative_keywords, set_ad_group_negative_keywords, or manage_negative_keyword_shared_sets, nor any prerequisites (e.g. sets must already exist).

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