yandex-direct

yd_execute

Execute Yandex Direct API actions by their ID. Use parameters from yd_search to manage campaigns and ads.

Instructions

Выполнить действие Yandex Direct API по ID.

Используй yd_search для получения ID и схемы параметров.

Args: action: ID действия из yd_search (например "campaigns-get", "ads-suspend") params_json: JSON-объект с параметрами согласно params_schema из yd_search

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "yd_execute"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`params_json`	No		{}

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Description confirms the tool is for executing actions (mutation), consistent with readOnlyHint=false. However, it does not disclose potential side effects, rate limits, or authentication requirements beyond what annotations imply. Lacks detail on return value or error behavior.

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?

Extremely concise: three sentences. First states purpose, second gives usage guidance, third explains parameters. No wasted words, front-loaded with key information.

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

Completeness4/5

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

Given that output schema exists and the tool is part of a pair with yd_search, the description is largely complete. It could briefly mention that results follow the output schema, but is sufficient for an agent using yd_search first.

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

Parameters4/5

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

Despite 0% schema description coverage, the description explains both parameters: action as an ID from yd_search, and params_json as a JSON object following the schema from yd_search. This adds significant meaning beyond the bare schema structure.

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?

Description explicitly states the tool executes a Yandex Direct API action by ID, and distinguishes from yd_search by referencing it for obtaining the ID and schema. The verb 'Выполнить' clearly indicates execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description instructs to use yd_search first to get the action ID and parameter schema, providing clear usage context. It does not explicitly list when not to use, but the guidance effectively implies the prerequisite workflow.

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

Deploy Server