Skip to main content
Glama
OlegRadinuk

Yandex Direct MCP Server

by OlegRadinuk

list_ad_groups

Retrieve ad groups for specified campaign IDs. Optionally set a limit on the number of results.

Instructions

List ad groups for the given campaign IDs.

Args: campaign_ids: One or more campaign IDs. limit: Max results (1–10000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idsYes
limitNo
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It correctly implies a read-only operation ('list'), but lacks detail on permissions, rate limits, or side effects. While the behavior is straightforward, additional transparency (e.g., 'This is a read-only operation') would improve the score.

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

Conciseness5/5

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

Two concise sentences, front-loaded with purpose. No extraneous information. Every word earns its place.

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 listing tool without an output schema, the description is mostly adequate. However, it lacks information about what is returned (e.g., ad group details) and assumes the agent knows the response format. More context on the output would make it complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must explain parameters fully. It does so: 'campaign_ids: One or more campaign IDs' and 'limit: Max results (1–10000).' This adds meaning beyond the schema's type-only definitions, including the valid range for limit.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'List ad groups for the given campaign IDs.' This specific verb+resource combination (list + ad groups) effectively distinguishes it from sibling tools like add_ad_groups, delete_ads, etc.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention any prerequisites, exclusions, or context for choosing list_ad_groups over other list or mutation tools.

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/OlegRadinuk/yandex-direct-mcp'

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