Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

Создать корректировки ставок

add_bid_adjustments

Create bid adjustments for campaigns or ad groups by device, demographics, retargeting, region, and more; set percentage modifiers from 0-1300, where 100 keeps bids unchanged.

Instructions

Создать корректировки ставок на кампаниях или группах. Коэффициент — проценты от ставки: 100 ничего не меняет, 0 отключает показы среза.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adjustments": "<adjustments>"
    },
    "name": "add_bid_adjustments"
  }
}

Input Schema

NameRequiredDescriptionDefault
adjustmentsYesКорректировки; каждая ставится каждому объекту из campaign_ids или ad_group_ids. Всего за вызов не больше 1000 корректировок — это цели, умноженные на виды
ad_group_idsNoГруппы, которым добавляются корректировки; вместо campaign_ids
campaign_idsNoКампании, которым добавляются корректировки; вместо ad_group_ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      +  "type": "boolean"
      +}
  3. First observedv1.6.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so mutability is known. The description adds real behavioral context beyond that — that the coefficient is a percentage where 100 is a no-op and 0 disables impressions for the segment — but it does not say whether existing adjustments are merged or replaced, whether the call is idempotent, or what permissions/limits apply.

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?

Two short sentences with no filler, front-loading the operation and then the coefficient semantics. Nothing is wasted, though the second sentence is the only part carrying non-obvious information.

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

Completeness3/5

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

The fully described 3-parameter schema and mutation annotations carry most of the load, and no output schema exists to explain. What remains uncovered is the key ambiguity for a mutation tool: how this differs from set_bid_adjustments and whether added adjustments accumulate alongside existing ones.

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 enum values, per-type fields (age, gender, region_id, serp_layout, income_grade, retargeting_condition_id) and the 0–1300 range are already fully documented. The description only reinforces bid_modifier semantics, adding the useful '0 disables impressions' nuance not spelled out in the schema, which is a marginal gain over the baseline.

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?

The description states a specific verb and resource: creating bid adjustments on campaigns or ad groups, and names the target scope (campaigns or groups). It is clearly a write operation distinct from get/delete siblings, but it never distinguishes itself from set_bid_adjustments, which is the sibling an agent is most likely to confuse it with.

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?

There is no when-to-use guidance at all: no statement of when to call add_bid_adjustments instead of set_bid_adjustments, no prerequisites, and no note that at least one of campaign_ids or ad_group_ids must accompany the adjustments array (the schema only requires adjustments). The agent must infer the routing itself.

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