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

yandex-direct-mcp-plus

by Pavelsiba

Динамические цели

list_dynamic_targets
Read-only

Retrieve targeting conditions for dynamic text ads, with optional filters by campaign, ad group, state, or specific dynamic target IDs.

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

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
statesNoФильтр по состоянию: ON или SUSPENDED
ad_group_idsNoЦели выбранных групп
campaign_idsNoЦели выбранных кампаний
dynamic_target_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

C2.5/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. Beyond that the description adds nothing: it does not mention pagination (the offset parameter references "LimitedBy предыдущей страницы"), result volume, or ordering. For a paginated list tool with six parameters, this leaves real behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler is front-loaded and easy to parse, so nothing is wasted. But it is undersized for a six-parameter paginated list tool, so brevity here reflects under-specification rather than disciplined concision.

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

Completeness2/5

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

No output schema exists, and the description does not compensate by describing the returned shape, the pagination contract, or the effect of combining the three ID filters with the states filter. For a tool of this complexity, the single sentence leaves the agent without what it needs to call it confidently.

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 every parameter — limit, offset, states, ad_group_ids, campaign_ids, dynamic_target_ids — is already documented in the schema, including the LimitedBy pagination pattern. The description adds no additional meaning, which is acceptable at the baseline when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and a resource ("Получить условия нацеливания динамических текстовых объявлений"), which is more specific than the bare title "Динамические цели". However, "условия нацеливания" is vague about what is actually returned — dynamic target records — and no sibling is named. The near-identical sibling manage_dynamic_targets makes read-vs-write ambiguity likely.

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 guidance on when to call this versus manage_dynamic_targets, the obvious mutation counterpart. No prerequisites, no mention of whether filters are required, and no indication of what to do with the result. Usage must be inferred entirely from the name.

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