Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Установить ставки

set_keyword_bids
Idempotent

Set search and network keyword bids in rubles at phrase, ad group, or campaign level for manual bid management. Run get_strategy first, then get_keyword_auction to price positions.

Instructions

Установить ставки (поиск/сети, в рублях) на уровне фраз, групп или кампаний (сервис Bids). Работает только при ручном управлении ставками: на автостратегии Директ назначает ставки сам, вызов пройдёт без ошибки, но на показы не повлияет. Сначала get_strategy, затем get_keyword_auction — сколько стоит нужная позиция.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidNoСтавка на поиске в рублях
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
context_bidNoСтавка в сетях (РСЯ) в рублях
keyword_idsNoСтавки на уровне фраз
ad_group_idsNoСтавки на все фразы указанных групп
campaign_idsNoСтавки на все фразы указанных кампаний

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
+  "type": "boolean"
+}
  2. First observedv1.6.1

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses a non-obvious silent-no-op failure mode under autostrategy, which is exactly the behavioral context annotations cannot convey, and it is consistent with readOnlyHint=false and idempotentHint=true. It stops short of covering permissions/auth requirements or confirmation behavior, so not a full 5.

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?

Front-loaded with purpose, then the key behavioral caveat, then the prerequisite chain in a tight, readable sequence. Every sentence earns its place; only slight density in the final clause keeps it from a 5.

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?

For a mutation tool with no output schema, it covers purpose, the critical when-it-does-nothing condition, and the prerequisite workflow. It does not describe what partial parameter combinations do or confirmation of applied bids, a minor gap.

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 description coverage is 100%, so the schema already documents bid, context_bid, keyword_ids, ad_group_ids, campaign_ids and dry_run. The description's 'поиск/сети, в рублях' and level scope add only marginal meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (установить) plus resource (ставки) with explicit scope: phrase/group/campaign level, search/network, rubles. The mention of manual vs. auto strategy context and the prerequisite tools clearly separates it from siblings like set_strategy and set_bid_adjustments.

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?

Gives explicit when-to-use ('работает только при ручном управлении ставками') and when-not (autostrategy assigns bids itself; the call succeeds but has no effect on impressions). It also routes the agent through prerequisites: get_strategy first, then get_keyword_auction.

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