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

yandex-direct-mcp-plus

by Pavelsiba

Общие наборы минус-фраз

list_negative_keyword_shared_sets
Read-only

Lists shared negative keyword sets for a Yandex.Direct account, returning all sets or specific set IDs to support campaign keyword management.

Instructions

Получить общие наборы минус-фраз аккаунта.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_negative_keyword_shared_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
set_idsNoКонкретные наборы; без них возвращаются все наборы аккаунта

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. 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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond restating 'get': no mention of pagination limits, result ordering, or whether sets from linked campaigns are included.

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 zero padding, and the resource is front-loaded. It is efficient, though it errs toward under-specification rather than excessive brevity.

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?

This is a simple read-only list tool with a fully documented schema and adequate annotations, so the description is almost complete. However, it omits any hint about pagination or the optional set_ids filtering behavior, which would help an agent call it correctly on first try.

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 limit, offset, and set_ids are already fully documented in the schema. The description's only contribution is the word 'аккаунта', which weakly implies account-level scope when set_ids is omitted, but that is already stated in 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?

The description states a specific verb and resource ('Получить общие наборы минус-фраз аккаунта'), which clearly identifies a read/list operation. It does not explicitly differentiate from the sibling 'manage_negative_keyword_shared_sets', leaving the mutating-vs-reading distinction to be inferred from the verb.

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 guidance on when to use this tool versus alternatives such as manage_negative_keyword_shared_sets or get_campaign_negative_keywords. No prerequisites, exclusions, or context are given beyond the tool existing to fetch account-level sets.

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