Skip to main content
Glama
skiddgoddamn

yandex-marketing-mcp

by skiddgoddamn

yd_negative_keywords_sets_add

Creates shared negative keyword sets (max 30) to reuse across campaigns for efficient exclusion of unwanted terms.

Instructions

Create shared negative keyword sets (max 30 total, reusable across campaigns).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSet name (max 255 chars)
negative_keywordsYesNegative keyword phrases
client_loginNoOptional. Override Client-Login for this call (agency multi-account).
Behavior2/5

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

No annotations provided. Description mentions a limit (max 30) but fails to disclose other behavioral details such as error handling, permissions needed, or whether creation replaces existing sets with the same name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, highly concise, with verb first. No redundant information.

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?

Tool has 3 parameters and no output schema. Description mentions a key constraint (max 30) but lacks guidance on return values, error scenarios, or how reusability works in practice.

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 coverage is 100%, so description adds no additional meaning beyond what the schema already provides. Description does not elaborate on parameter usage or formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (Create), resource (shared negative keyword sets), and a constraint (max 30 total, reusable across campaigns). Distinguishes from sibling tools like delete and update.

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

Usage Guidelines4/5

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

Provides context that sets are shared and reusable, indicating when to use this tool. However, lacks explicit guidance on when not to use it or alternatives for campaign-level negatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skiddgoddamn/yandex-marketing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server