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

yandex-direct-mcp-plus

by Pavelsiba

Задать расписание показов

set_time_targeting
Idempotent

Set a Yandex.Direct campaign ad schedule by defining days, hours, hourly bid adjustments, holidays, and time zone; the full schedule is replaced, so uncovered hours receive no impressions.

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": {
      "campaign_id": "<campaign_id>",
      "schedule": "<schedule>"
    },
    "name": "set_time_targeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleYesПравила показов. Часы, не покрытые ни одним правилом, показов не получают — расписание задаётся целиком, а не дополняется. Правила применяются по порядку, последнее переопределяет предыдущие
time_zoneNoЧасовой пояс кампании, например Europe/Moscow. Допустимые значения — в справочнике list_time_zones. Не задан — остаётся прежним
campaign_idYesID кампании, десятичная строка
holiday_end_hourNoЧас окончания показов в праздники, не включая его, 1–24
holiday_start_hourNoЧас начала показов в праздники включительно, 0–23
holiday_bid_percentNoКоэффициент к ставке в праздники, % от текущей: 10–200 с шагом 10. Ноль запрещён — показы отключает suspend_on_holidays
suspend_on_holidaysNotrue — в праздники показов нет; false — идут по правилам holiday_*. Не задан — праздники отдельно не настраиваются
consider_working_weekendsNoПоказывать ли в рабочие выходные по расписанию переносимого буднего дня; false — по расписанию выходного

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.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true and openWorldHint=true; they say nothing about overwrite semantics. The description fills that gap with a prominent warning that the schedule is replaced entirely and hours outside the supplied rules receive no impressions, which is the single most consequential behavior for an agent to know before calling.

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 sentences: the first establishes scope and fields, the second front-loads the destructive replacement warning with a visible marker. No filler and no repetition of what the schema already says.

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 an eight-parameter mutation with no output schema and no annotations covering side effects, the description supplies the critical missing piece: whole-schedule replacement and the resulting dark hours. Remaining gaps, such as interaction rules with holiday fields or permission requirements, are already handled by the unusually rich schema.

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 schema already documents each field in detail, including the half-open end_hour, the 0-200 step-10 bid percent, and why holiday_bid_percent cannot be zero. The description adds no parameter-level detail beyond restating the covered domains, 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?

The description states a specific verb and resource ("Задать расписание показов кампании") and enumerates the dimensions it controls: days, hours, hourly coefficients, holidays, time zone. That lets an agent distinguish it from the read counterpart get_time_targeting without inspecting the schema, although the description never names that sibling 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?

There is no explicit statement of when to use this versus get_time_targeting, nor of preconditions such as campaign ownership or read-before-write. The valuable implicit guidance it does give is the replacement warning, which tells the agent this is a full-overwrite operation rather than a patch.

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