Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Удалить корректировки ставок

delete_bid_adjustments
Destructive

Remove specified bid adjustments by ID, reverting bids to base values. Deletion is permanent and cannot be undone.

Instructions

Удалить корректировки по их ID. Ставка среза возвращается к базовой; отменить удаление нельзя.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
adjustment_idsYesКорректировки, которые нужно удалить; ID берутся из get_bid_adjustments

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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the agent knows the operation is destructive. The description adds genuinely new behavioral context beyond that: the bid slice reverts to its base value and the deletion is irreversible. It does not mention auth requirements or batch limits, but for a delete tool this is solid added value.

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 short sentences, front-loaded with the action, and every clause carries information (what is deleted, by what key, side effect, irreversibility). No filler.

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 destructive, no-output-schema tool whose annotations and schema are already rich, the description covers the critical irreversible side effect. It omits any note on dry_run as the safe pre-check and on partial-failure behavior across a large ID list, which are minor gaps.

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% and both parameters are fully documented in the schema, including the dry_run semantics and the source of adjustment_ids. The description only restates that deletion is by ID, adding no 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (delete bid adjustments) with the keying method ('по их ID'), which is unambiguous. It does not explicitly name siblings like set_bid_adjustments or add_bid_adjustments, but 'delete' is distinct enough to separate it from the other bid-adjustment tools.

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?

The description gives no when-to-use guidance, no mention of the dry_run verification path, and no prerequisites or alternatives. The only routing hint ('ID берутся из get_bid_adjustments') lives in the schema, not the description.

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