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

yandex-direct-mcp-plus

by Pavelsiba

Списки ретаргетинга

list_retargeting_lists
Read-only

Retrieve retargeting conditions and audience segments with their rules and application scope; filter by type or specific IDs and paginate results.

Instructions

Получить условия ретаргетинга и подбора аудитории с правилами и областью применения.

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_retargeting_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
typesNoФильтр по типу: RETARGETING — цели Метрики, AUDIENCE — сегменты Аудиторий
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
retargeting_list_idsNoКонкретные условия; без них возвращаются все

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that each returned item carries rules and a scope of application ("с правилами и областью применения"), which is useful given there is no output schema, but it says nothing about paging behavior or result volume.

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?

A single short sentence with the verb front-loaded and no redundant clauses. The trailing phrase "с правилами и областью применения" is slightly vague but still carries information about returned content, so little 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?

For a simple four-parameter, entirely optional-filter list tool with no output schema, the definition is minimally adequate: filters and safety are covered by schema and annotations. What remains missing is any notion of pagination behavior or the practical difference from adjacent audience-listing siblings.

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%, including the enum meanings for types and the LimitedBy-based offset convention, so the schema does the heavy lifting. The description contributes no additional meaning for limit, offset, types, or retargeting_list_ids, making the baseline 3 appropriate.

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 uses a clear verb+resource pairing ("Получить условия ретаргетинга и подбора аудитории") that maps to a list operation over retargeting/audience conditions. It does not, however, distinguish this tool from nearby siblings such as list_audience_targets or list_dynamic_targets, which also surface audience-related entities.

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 explicit when-to-use guidance: nothing says this is the read path before update_retargeting_lists / delete_retargeting_lists, and nothing separates it from list_audience_targets. The only cue is the "list_" prefix, leaving the agent to infer usage entirely.

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