Skip to main content
Glama
skiddgoddamn

yandex-marketing-mcp

by skiddgoddamn

yd_retargeting_lists_get

Get retargeting lists for Yandex Direct by providing list IDs. Enables audience management for advertising campaigns.

Instructions

Get retargeting lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNo
client_loginNoOptional. Override Client-Login for this call (agency multi-account).
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'Get retargeting lists', implying a read operation but lacking details on pagination, authentication, or return format. Minimal transparency.

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?

The description is very concise at one sentence, but it is also under-specified. It earns its place but does not provide enough value for the length.

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?

Given the lack of output schema and annotations, the description is too brief. It does not explain what the tool returns, how ids work, or any constraints. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention any parameters, adding no meaning beyond the input schema. Schema coverage is 50% (client_login has description), but the tool description fails to explain the 'ids' parameter, which is crucial for filtering.

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 clearly states the verb 'Get' and resource 'retargeting lists', distinguishing it from sibling tools like add and delete. It is specific but lacks additional context about scope.

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?

No guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context about when to use this retrieval tool over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skiddgoddamn/yandex-marketing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server