Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

set_time_targeting
Idempotent

Set campaign ad schedule: days, hours, hourly bid coefficients, holiday rules, and time zone. Replaces the entire schedule, so uncovered hours get no impressions.

Instructions

Задать расписание показов кампании: дни, часы, почасовые коэффициенты, праздники и часовой пояс. ⚠️ Расписание заменяется целиком: часы вне переданных правил показов не получат.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
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. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
+  "type": "boolean"
+}
  2. First observedv1.6.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and openWorldHint=true, so safety/idempotency is covered. The description adds the critical non-obvious trait beyond annotations: the schedule is replaced wholesale and uncovered hours receive no impressions. It omits auth/permission prerequisites, so not a full 5.

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 tight sentences, front-loaded with the action and its scope, followed by the destructive-replacement warning flagged with an emoji. No filler; every clause carries information.

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 9-parameter mutation tool with a fully documented schema and no output schema, the description supplies the essential replace-all semantics and the configurable dimensions. It lacks any note on return behavior/permission requirements, but annotations and schema cover most of the remaining burden.

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%, so each parameter (dry_run, schedule, time_zone, holiday_*, suspend_on_holidays, consider_working_weekends) is already fully documented in the schema. The description only restates the configurable facets at a high level, adding no syntax or format detail beyond the schema — baseline 3.

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?

Specific verb (set / задать) plus resource (расписание показов кампании) with an enumeration of the configurable facets (days, hours, hourly coefficients, holidays, time zone). The write verb cleanly distinguishes it from the read-side sibling get_time_targeting without opening a schema.

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 implies usage (setting a campaign schedule) and warns that the schedule is replaced entirely, but never states when to reach for this tool versus alternatives such as get_time_targeting (inspect first) or update_campaign. Guidance is implied rather than explicit.

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