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

yandex-direct-mcp-plus

by Pavelsiba

Корректировки ставок

get_bid_adjustments
Read-only

Retrieve bid adjustments for Yandex.Direct campaigns or ad groups by device, gender, age, audience, region, income level, and placement to audit or tune targeting.

Instructions

Получить корректировки ставок кампании или группы: устройства, пол и возраст, аудитории, регионы, платёжеспособность, размещение.

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": {
      "levels": "<levels>"
    },
    "name": "get_bid_adjustments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
typesNoФильтр по типу корректировки
levelsYesУровни корректировок: CAMPAIGN и/или AD_GROUP
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
ad_group_idsNoГруппы, корректировки которых нужно получить
campaign_idsNoКампании, корректировки которых нужно получить
adjustment_idsNoКонкретные корректировки по их ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observedv1.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that results span six adjustment domains, which is useful scoping context, but says nothing about pagination (offset/limit semantics), result volume limits, or ordering behavior.

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 the scope list appended; no filler. It is efficient, though the trailing enumeration could be shortened without losing meaning.

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?

Missing a few facts an agent would want: that 'levels' is required, that campaign_ids caps at 10 while ad_group_ids caps at 1000, and how to page. For a straightforward read-only lister with a fully documented schema, this is a modest but real 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 coverage is 100%, so limit, offset, levels, types, ids are all documented in the schema itself. The description's category list loosely maps onto the types enum (платёжеспособность→INCOME_GRADE_ADJUSTMENT, размещение→SERP_LAYOUT_ADJUSTMENT), which is mildly helpful, but it never mentions the required 'levels' parameter or the id filters.

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 opens with a specific verb+resource ('Получить корректировки ставок') and enumerates the adjustment categories covered (devices, demographics, audiences, regions, income, placement). This clearly separates it from the write siblings add_bid_adjustments/set_bid_adjustments/delete_bid_adjustments, though it never names them 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?

Usage is only implied by the read verb 'Получить' — an agent can infer this is the retrieval counterpart to set_bid_adjustments, but nothing states when to use this versus those siblings, nor any prerequisites such as needing campaign/ad group IDs first.

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