Skip to main content
Glama
askads

Yandex Direct MCP

Set keyword bids

set_keyword_bids
Idempotent

Set manual search and network bids for keywords, ad groups, or campaigns to control cost-per-click.

Instructions

Sets manual search/network bids on keywords, or on all keywords in given ad groups or campaigns (keywordbids/set). Bids are in account currency units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidsYesEach item needs one target id and at least one of bid/contextBid.
Behavior3/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. Description adds currency unit context but no additional behavioral details (e.g., overwrite behavior, permissions). No contradiction with annotations.

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?

Two concise sentences with front-loaded action and no unnecessary words. Every sentence adds value.

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

Completeness4/5

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

Adequate for a setting tool with 1 parameter (array of objects). Schema covers parameters well. Minor omission: no mention of return value or validation rules, but acceptable given no output schema.

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% with descriptions for all parameters. Description adds no parameter-specific meaning beyond schema; baseline score of 3 is appropriate.

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?

Specific verb 'Sets', resource 'manual search/network bids on keywords', scope 'or on all keywords in given ad groups or campaigns', and API endpoint identifier. Clearly distinguishes from sibling tools like set_bid_modifiers.

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

Usage Guidelines3/5

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

Description implies usage for setting keyword bids but provides no explicit when-to-use, when-not-to-use, or alternatives. Lacks guidance distinguishing from sibling tools like set_bid_modifiers.

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

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