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

yandex-direct-mcp-plus

by Pavelsiba

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

delete_bid_adjustments
Destructive

Remove specific bid adjustments by providing their IDs. This action resets the targeted bid to its base value and cannot be reversed.

Instructions

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

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": {
      "adjustment_ids": "<adjustment_ids>"
    },
    "name": "delete_bid_adjustments"
  }
}

Input Schema

NameRequiredDescriptionDefault
adjustment_idsYesКорректировки, которые нужно удалить; ID берутся из get_bid_adjustments

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

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversible nature is known structurally. The description still adds real behavioral context: the bid share reverts to the base value, and the deletion is explicitly unrecoverable - that consequence is not derivable from the annotations.

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 tight sentences, front-loaded with the action and followed by the effect and the irreversibility warning. No filler, though the phrasing could be slightly more compact.

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 one-parameter destructive mutation, the definition covers what gets removed, the resulting state change, and the lack of undo, while annotations carry the safety profile and the schema carries ID sourcing and limits. Minor gaps remain around bulk partial-failure behavior, but nothing essential is missing.

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% and the single parameter already documents the ID pattern, 1-10000 item bounds, and the get_bid_adjustments source. The description only restates 'по их ID' and adds nothing 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 and resource ('Удалить корректировки') plus the selector ('по их ID'), so the agent knows exactly what is being removed. It does not name or distinguish itself from siblings such as set_bid_adjustments, which could also be used to reset an adjustment.

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?

Usage is implied by 'удалить' - use this when an adjustment should be removed rather than modified. No explicit when-to-use/when-not guidance and no mention of the add_/set_ siblings as alternatives (e.g., setting a 0% adjustment instead of deleting).

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