yandex-api-mcp

Overview Schema Source Related Servers Discussions Admin

direct.hf.set_adgroup_negative_keywords

Set negative keywords for Yandex Direct ad groups to prevent ads from showing on irrelevant search terms. Preview changes with dry-run before applying.

Instructions

Human-friendly: set ad group negative keywords.

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": "direct.hf.set_adgroup_negative_keywords"
  }
}

Input Schema

Name	Required	Description
`apply`	No
`items`	No
`dry_run`	No
`account_id`	No	Project profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
`adgroup_id`	No
`campaign_id`	No
`adgroup_name`	No
`campaign_name`	No
`direct_client_login`	No	Override Direct Client-Login for this call (agency multi-project support).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden and provides essentially none. It does not say whether existing negative keywords are replaced or appended, what apply/dry_run actually do, or what permissions are required for this mutation.

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

Conciseness3/5

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

One short sentence with no redundancy, but the 'Human-friendly:' prefix is filler that consumes the only available space, and the brevity is under-specification rather than effective concision.

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

Completeness1/5

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

A 9-parameter mutation tool with no annotations, no output schema, and low schema coverage needs far more than a tautological sentence. An agent cannot safely invoke this without understanding apply/dry_run and the ad group identifier fields.

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

Parameters1/5

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

Nine parameters at 22% schema coverage, and the description mentions none of them. Critically, the apply and dry_run booleans — which determine whether the call is a preview or a real mutation — are left completely unexplained in both the schema and the description.

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?

States a specific verb and resource ('set ad group negative keywords'), so the mutation target is unambiguous. However, it does not distinguish itself from the near-identical sibling direct.hf.set_campaign_negative_keywords or mention scope relative to find_keywords/suggest_negative_keywords.

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?

No when-to-use guidance, no prerequisites (e.g., that the ad group must already exist), and no mention of the dry_run/apply workflow this family clearly uses. The agent must infer everything from the name alone.

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

Deploy Server