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

yandex-direct-mcp-plus

by Pavelsiba

Расписание показов кампании

get_time_targeting
Read-only

Retrieve a campaign's time targeting settings, including time zone, weekly ad schedule, hourly bid coefficients, and holiday configuration by campaign ID.

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>"
    },
    "name": "get_time_targeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesID кампании, десятичная строка

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

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=true annotations already establish that this is a safe, non-mutating read against external account data. The description adds some value by revealing which sub-structures come back (hours per weekday, hourly coefficients, holidays), but it says nothing about authentication needs, what happens for a campaign with no schedule configured, or any failure mode.

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?

One compact sentence with no filler, and the resource is front-loaded before the enumerated components. It is a nominal fragment rather than a full statement, which slightly weakens front-loading of the action, but nothing is wasted.

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 single-parameter read tool with no output schema, enumerating the returned schedule components (time zone, weekday hours, coefficients, holidays) is essentially the needed context. The remaining gap is routing against set_time_targeting and list_time_zones, which the description leaves unaddressed.

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 campaign_id is documented in the schema with its decimal-string pattern, so the baseline is 3. The description does not mention campaign_id at all, adding no meaning about format, required existence, or scope beyond what the schema already states.

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 names the exact resource (campaign time targeting) and enumerates its components: time zone, display hours by weekday, hourly coefficients, and holiday settings. That is specific enough to distinguish it from a general campaign getter, but it never uses a verb like 'get/return', so it reads as a content label rather than an action, and it does not explicitly separate itself from the mutating sibling set_time_targeting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. The description never says to call this to inspect a schedule before calling set_time_targeting, nor does it mention any alternative such as list_time_zones or get_campaign, so the agent must infer routing from the name alone.

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