Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Изменить корректировки ставок

set_bid_adjustments
Idempotent

Update the bid modifier percentages for existing Yandex.Direct bid adjustments by ID, so you can tune campaign bids without recreating them.

Instructions

Изменить коэффициенты существующих корректировок по их ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
adjustmentsYesКорректировки и их новые коэффициенты

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds no behavioral context beyond that: it says nothing about dry_run preview behavior, batch limits, validation semantics, or what happens to omitted fields.

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 front-loaded sentence with no filler or redundancy. It is appropriately terse for the tool, though its brevity means it is also doing little structural work beyond naming the operation.

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 input schema and annotations are thorough, and no output schema exists, so the description need not explain return values. However, for a mutation tool with a dry_run preview and bulk array of up to 1000 adjustments, the description omits important usage context, making it merely minimum viable.

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%, with rich parameter docs for dry_run, adjustment_id, and the bid_modifier range (0–1300). The description mentions ID and coefficients but adds no syntax, format, or constraint detail beyond what the schema already provides, so the baseline of 3 applies.

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 (коэффициенты существующих корректировок) scoped by ID. The word 'существующих' distinguishes it from add_bid_adjustments and delete_bid_adjustments, though it does not name those alternatives explicitly.

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?

Implies use only when existing adjustment IDs are known and their coefficients need changing. It gives no explicit when-not guidance and never mentions the sibling tools (add_bid_adjustments, delete_bid_adjustments) or the dry_run preview option, leaving selection between related tools to inference.

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