Skip to main content
Glama
askads

Yandex Direct MCP

Ad action

ad_action
Destructive

Moderate, suspend, resume, archive, unarchive, or delete ads by providing their IDs.

Instructions

Performs a lifecycle action on ads by id: moderate, suspend, resume, archive, unarchive or delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesAd ids to act on.
actionYes
Behavior3/5

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

Annotations already provide destructiveHint=true. Description lists actions but doesn't disclose side effects (e.g., permanence of delete) or error handling. Adequate but minimal extra context.

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?

Single sentence front-loading the purpose and enumerating actions. No filler or redundant information.

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 batch-action tool with no output schema, description lacks details on return behavior, per-id status, or safety notes. Annotations partially compensate but still incomplete.

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?

Schema coverage is 50% (only 'ids' has description). Description repeats action list from schema without adding new meaning. No help for missing parameter descriptions.

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?

Clearly states it performs lifecycle actions on ads (moderate, suspend, resume, archive, unarchive, delete), distinguishing it from sibling tools like campaign_action or keyword_action.

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 explicit guidance on when to use this tool vs alternatives like campaign_action or keyword_action. Does not specify prerequisites or excluded scenarios.

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

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