Skip to main content
Glama
OlegRadinuk

Yandex Direct MCP Server

by OlegRadinuk

add_negative_keywords

Set the complete list of negative keywords for Yandex Direct campaigns or ad groups, replacing any existing ones. Retrieve current list first, merge with new terms, then apply.

Instructions

Add negative (minus) keywords to campaigns or ad groups.

Sets the COMPLETE list of negative keywords — merges with existing ones. First call list_ad_groups or list_campaigns to get current NegativeKeywords, then include existing + new ones in your update.

Args: campaign_updates: List of campaign negative keyword updates: [{"Id": , "NegativeKeywords": {"Items": ["слово1", "слово2"]}}] ad_group_updates: List of ad group negative keyword updates: [{"Id": , "NegativeKeywords": {"Items": ["слово1", "слово2"]}}]

confirm: True to execute; False returns dry-run plan.

IMPORTANT: This REPLACES the current negative keyword list for each object. To add incrementally: first read current list, merge, then update. SYNTAX: Negative keywords must NOT have the minus sign — just the word/phrase. E.g. Items: ["бесплатно", "своими руками", "скачать"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_updatesNo
ad_group_updatesNo
confirmNo
Behavior5/5

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

Discloses that the tool replaces the complete list of negative keywords, not appends, and explains the syntax convention (no minus sign). No annotations provided, so description carries full burden.

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?

Well-structured with bullet points and examples; every sentence adds value without being verbose.

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

Completeness5/5

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

Comprehensive description covering behavior, prerequisites, dry-run, and syntax, despite no output schema. Addresses how to use with sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond the schema by providing detailed structure examples for campaign_updates and ad_group_updates, including required fields like Id and NegativeKeywords.Items.

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 it adds negative keywords to campaigns or ad groups, and differentiates from sibling tools like add_keywords by specifying 'negative'.

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

Usage Guidelines5/5

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

Provides explicit when-to-use instructions, including prerequisite calls to list_ad_groups or list_campaigns, and explains the confirm parameter for dry-run testing.

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/OlegRadinuk/yandex-direct-mcp'

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