Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Задать ставки ключевых фраз

set_keyword_bids
Idempotent

Sets manual search and network bids for individual keywords or all keywords in selected ad groups or campaigns, using account currency. Use one target type per call.

Instructions

Задаёт ручные ставки на поиске и в сетях для ключевых фраз либо для всех фраз указанных групп объявлений или кампаний (keywordbids/set). Ставки — в валюте аккаунта. Тип цели один на весь вызов: все элементы bids используют только keywordId, только adGroupId или только campaignId; для целей разных типов нужны отдельные вызовы.

Input Schema

NameRequiredDescriptionDefault
bidsYesВ каждом элементе ровно один целевой id (keywordId, adGroupId или campaignId) и хотя бы одно из полей bid/contextBid. Тип id одинаков во всех элементах: смешивать keywordId, adGroupId и campaignId в одном вызове нельзя.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.0
    • changedInput schema / properties / bids / description
      Previous value: -"В каждом элементе нужен один целевой id и хотя бы одно из полей bid/contextBid."New value: +"В каждом элементе ровно один целевой id (keywordId, adGroupId или campaignId) и хотя бы одно из полей bid/contextBid. Тип id одинаков во всех элементах: смешивать keywordId, adGroupId и campaignId в одном вызове нельзя."
  2. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / client_login
      Added value: +{
+  "description": "Логин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.",
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._@-]{0,99}$",
+  "type": "string"
+}
  3. Changed6 schema fields changedv1.5.1
    • changedInput schema / properties / bids / description
      Previous value: -"Each item needs one target id and at least one of bid/contextBid."New value: +"В каждом элементе нужен один целевой id и хотя бы одно из полей bid/contextBid."
    • changedInput schema / properties / bids / items / properties / adGroupId / description
      Previous value: -"Target all keywords in an ad group."New value: +"Применить ко всем фразам группы объявлений."
    • changedInput schema / properties / bids / items / properties / bid / description
      Previous value: -"Search bid in currency units."New value: +"Ставка на поиске в валюте аккаунта."
    • changedInput schema / properties / bids / items / properties / campaignId / description
      Previous value: -"Target all keywords in a campaign."New value: +"Применить ко всем фразам кампании."
    • changedInput schema / properties / bids / items / properties / contextBid / description
      Previous value: -"Network bid in currency units."New value: +"Ставка в сетях в валюте аккаунта."
    • changedInput schema / properties / bids / items / properties / keywordId / description
      Previous value: -"Target a single keyword."New value: +"Применить к одной ключевой фразе."
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but idempotent, non-destructive, open-world mutation. The description adds genuinely useful behavior: bids are in account currency, the operation sets manual bids, and the target-type homogeneity rule means a call cannot partially apply across id types. It still omits whether existing/automatic bids are overwritten and what happens on partial failure.

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 dense sentences, front-loaded with the verb and resource, then the call-structure constraint. Nothing is redundant given what the schema covers, and no sentence is 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 mutation tool with full annotation coverage, a fully documented schema, and no output schema, the description supplies the essential operational facts (currency, one target type per call, separate calls). It could still state whether manual bids replace automated strategies or what the response contains, but nothing critical to correct invocation 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 nested bids schema already documents bid/contextBid currency semantics, the exactly-one-target-id rule, and the homogeneous-id-type rule. The description restates these rather than adding new meaning, so the baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description names a specific verb and resource (sets manual search and network bids for keywords) and scopes it to individual keywords, all keywords of ad groups, or all keywords of campaigns, plus the API path keywordbids/set. This clearly separates it from bid-modifier and keyword-action siblings without requiring the schema to be opened.

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?

The description clearly states a hard usage constraint: one target type per call, and separate calls for mixed target types. However, it never says when to prefer this over related tools such as set_bid_modifiers or keyword_action, nor does it mention prerequisites like a manual bidding strategy. Usage is implied rather than routed.

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