Skip to main content
Glama
5iNeX

yandex-api-mcp

by 5iNeX

direct.hf.set_keyword_bids_bulk

Set a uniform ruble bid for all keywords in a Yandex Direct campaign or adgroup; use dry-run to preview or apply to update bids in bulk.

Instructions

Human-friendly: set a uniform bid (rubles) for all keywords in a campaign/adgroup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applyNo
bid_rubNo
dry_runNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
adgroup_idNo
campaign_idNo
direct_client_loginNoOverride Direct Client-Login for this call (agency multi-project support).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It omits that this overwrites existing bids for every keyword in scope, says nothing about the apply/dry_run flags (a safety-relevant pair for a mutation tool), and doesn't mention required permissions or how failures on individual keywords are handled.

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 tight sentence with the scope constraint front-loaded after the verb; no wasted words. It is under-specified rather than verbose, which is a different problem.

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

Completeness2/5

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

For a bulk mutation tool with no annotations, no output schema, and mostly undocumented parameters, the description is not sufficient. The absence of any dry_run/apply explanation is the most consequential gap for an agent deciding how to invoke it safely.

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

Parameters2/5

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

Schema coverage is only 29% across 7 parameters, so the description must compensate and largely doesn't. It clarifies that bid_rub is in rubles and that campaign/adgroup scope is selected, but gives no meaning to apply, dry_run, direct_client_login beyond the schema, or the mutual exclusivity of campaign_id and adgroup_id.

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+resource (set keyword bids) with scope (all keywords in a campaign/adgroup) and currency (rubles). Implicitly distinguishes from the singular sibling direct.hf.set_keyword_bid via 'bulk', but never names or contrasts that sibling explicitly.

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 prerequisite for campaign_id vs adgroup_id, and no routing toward the singular set_keyword_bid or bid_sweep tools. The only hint is 'for all keywords in a campaign/adgroup', which implies bulk scope but not when that scope is preferred.

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

Deploy Server

Other Tools