Skip to main content
Glama
Sign In
yandex-api-mcp

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.apply_plan

Apply a previously planned Yandex Direct change plan by plan_id, with optional dry_run and account overrides. Requires apply=true and pro mode.

Instructions

Human-friendly: apply a previously planned Direct change plan (pro-only, apply=true).

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": {
      "plan_id": "<plan_id>",
      "apply": "<apply>"
    },
    "name": "direct.hf.apply_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyYes
dry_runNo
plan_idYesOpaque plan id returned by direct.hf.plan_changes.
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
direct_client_loginNoOverride Direct Client-Login for this call (agency multi-project support).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden. It discloses the pro-only gate and the apply=true requirement, which is useful. But for a mutation tool that commits planned changes it says nothing about reversibility, side effects, permissions, or what actually changes, and 'Human-friendly' adds no behavioral information.

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

Conciseness4/5

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

A single compact sentence with the operation front-loaded after a short label. It is efficient and wastes no words, though the leading 'Human-friendly:' is mild filler rather than substantive content.

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?

For a no-annotation mutation tool with no output schema and 60% param coverage, the description is too thin. It should state the prerequisite (must plan first), the effect of committing a plan, and whether it is reversible. What exists is accurate but incomplete for the tool's complexity.

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 coverage is 60% - plan_id, account_id, and direct_client_login are documented in the schema, while apply and dry_run are not. The description adds meaning by tying apply to 'apply=true,' partially compensating for the undocumented apply param, but dry_run is left unexplained. Baseline 3 is appropriate.

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?

States a clear verb+resource: 'apply a previously planned Direct change plan.' It distinguishes itself as the apply step of the planning workflow (vs. direct.hf.plan_changes) and names the operation precisely. It lacks explicit contrast with the other 'apply'-style siblings like audience.hf.apply_activation_plan or bid_sweep_run, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

The phrase 'previously planned' implies you must call direct.hf.plan_changes first, and it flags a pro-only constraint. However it gives no explicit when-to-use vs when-not, no prerequisite statement, and doesn't distinguish the direct.bid_sweep_run path or audience apply tools. Usage is left to inference.

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

Deploy Server

Other Tools