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

yandex-direct-mcp-plus

by Pavelsiba

Справочник часовых поясов

list_time_zones
Read-only

Retrieve Yandex.Direct time zone references for campaign and time targeting setup, with case-insensitive filtering by zone code or name.

Instructions

Справочник часовых поясов (TimeZones) для set_time_targeting и create_campaign. Фильтр по коду или названию.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_time_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько часовых поясов вернуть, максимум 500
searchNoФильтр по коду или названию пояса: подстрока без учёта регистра, например «moscow» или «Екатеринбург»

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.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered outside the description. The description adds no behavior beyond that: nothing about the default limit of 50, the 500 ceiling, truncation behavior, or the fields (code, name) returned. For a read-only catalog tool this is a modest but real gap.

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?

Two short sentences, with the resource and consumers front-loaded and zero filler. The parenthetical "(TimeZones)" duplicates the title somewhat, but that is a minor redundancy rather than wasted space.

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 trivial read-only lookup with two fully documented optional parameters and safety annotations, an agent has what it needs to call the tool. The remaining omission is what the result rows contain and whether results are ordered or capped, which matters slightly more because there is no output 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%, so both parameters are already documented with substring semantics and an example, and 3 is the appropriate baseline. The description's "Фильтр по коду или названию" merely restates the search parameter and says nothing about limit, adding no meaning beyond the schema.

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?

Names the resource precisely ("Справочник часовых поясов (TimeZones)") and makes clear it is a lookup catalog, with the two consumer tools named. This separates it from siblings like get_regions and set_time_targeting. It stops short of a verb like "list/return", but the noun "справочник" plus the filter clause leaves little ambiguity.

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?

Attaching it to set_time_targeting and create_campaign implies the workflow (resolve a zone code before writing targeting), which is useful context for selection. However, it never says when NOT to use it versus get_regions, nor what to do if the search returns nothing, so the 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.