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

yandex-direct-mcp-plus

by Pavelsiba

Справочник регионов

get_regions
Read-only

Look up Yandex.Direct GeoRegion codes for ad targeting, filter regions by name, and resolve same-named cities via parent hierarchy.

Instructions

Справочник кодов регионов (GeoRegions) для таргетинга. Фильтр по названию, 225 = Россия. with_parents=true показывает вложенность и различает одноимённые города.

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": "get_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько регионов вернуть, максимум 500
searchNoФильтр по названию региона: подстрока без учёта регистра, например «москва»
with_parentsNoПоказать, во что вложен регион (Новосибирск → Новосибирская область, Россия) — так различаются одноимённые города. По умолчанию выключено; требует search. Ищет при этом сам Директ — по похожему названию, а не подстрокой, как кэшированный справочник

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.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read, so the description's job is lighter. It adds one genuinely useful non-schema fact ('225 = Россия'), but the with_parents explanation largely repeats what the schema already documents, and it says nothing about rate limits, caching freshness, or response shape.

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, front-loaded with the resource identity and the key constant. The abrupt mid-sentence switch to 'with_parents=true' mixed into Russian prose is slightly rough, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (read-only, 3 optional params, no output schema), so it does not need much, and the description covers filtering and nesting. However, with no output schema the description should say what a result looks like (region id + name) and whether limit paginates, which it does not.

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 the schema already explains limit, search, and with_parents in detail, including the 'requires search' constraint and the matching-semantics caveat. The description only adds the 225=Russia constant, which is helpful but marginal; 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 names the resource precisely: a reference/lookup of region codes (GeoRegions) used for targeting, which is a specific verb-plus-resource statement. It does not explicitly say it returns a list, and it does not differentiate itself from any sibling (e.g., list_time_zones), so it stops short of a 5.

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 phrase 'для таргетинга' plus 'Фильтр по названию' implies the lookup workflow (finding region IDs to use in targeting), but there is no explicit when-to-use, when-not, or named alternative. Usage is inferable rather than stated.

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