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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.bid_sweep_run

Apply one bid sweep step from a saved plan to adjust Yandex Direct bids; requires apply=true, pro mode, and sandbox-only execution.

Instructions

Human-friendly: apply one bid sweep step (pro-only, apply=true, sandbox-only).

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>",
      "step_index": "<step_index>",
      "apply": "<apply>"
    },
    "name": "direct.hf.bid_sweep_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyYes
dry_runNo
plan_idYesOpaque plan id returned by direct.hf.bid_sweep_plan.
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
step_indexYes0-based step index to apply.
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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool is pro-only and sandbox-only and requires apply=true, which covers authorization and safety scope. However, it doesn't explain what gets modified, whether changes are reversible, or rate/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.

Conciseness4/5

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

The description is a single, front-loaded sentence with dense constraint information. The only questionable element is the 'Human-friendly:' prefix, which is vague and slightly reduces efficiency.

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 mutation tool with no annotations, no output schema, and 6 parameters, the description is quite terse. It does disclose critical safety constraints (sandbox-only, pro-only), but it omits side effects, prerequisites beyond the schema's plan_id link, and error handling.

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 description coverage is 67%, so the schema documents most parameters. The description adds meaning for the apply parameter by requiring 'apply=true', but it does not mention dry_run, and provides no additional semantics beyond 'one step' for step_index.

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 states a specific verb ('apply') and resource ('one bid sweep step'), so the core action is clear. However, it does not explicitly differentiate itself from siblings like direct.hf.bid_sweep_plan or direct.hf.apply_plan, and the 'Human-friendly' prefix is vague.

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?

It gives explicit conditions for use: 'pro-only, apply=true, sandbox-only'. This tells the agent when the tool is applicable and when it is not, but it does not name alternatives or explicitly say to use it after bid_sweep_plan.

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