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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.pause_campaigns

Pause Yandex Direct campaigns by ID or name. Supports dry-run and apply to preview or execute suspension.

Instructions

Human-friendly: suspend campaigns (by id or name).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "direct.hf.pause_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
dry_runNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
campaign_idsNo
campaign_nameNo
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

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a state-mutating operation. It never says the suspension is reversible, what permissions/account context are needed, or — most importantly — that the 'apply' and 'dry_run' flags govern whether anything actually changes.

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

Conciseness3/5

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

It is a single short sentence and front-loads the action, so it is not bloated. However, the filler 'Human-friendly:' prefix consumes space while the safety flags go unmentioned, making it terse rather than efficient.

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?

A mutation tool with no annotations, no output schema, and an undocumented apply/dry_run pair is significantly under-specified. An agent cannot safely determine whether a call executes or merely previews.

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 only 33%; only account_id and direct_client_login are documented. The description covers the id/name selectors but is silent on apply, dry_run, and campaign_ids format, leaving the safety-critical flags undocumented in both places.

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 specific verb and resource ('suspend campaigns') plus the two selection mechanisms ('by id or name'), which cleanly separates it from siblings like direct.hf.resume_campaigns and direct.hf.archive_campaigns. The 'Human-friendly:' prefix adds no information, and no sibling is named explicitly.

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 indication of when to pause versus archive or moderate, no prerequisites, and no mention of the closely related direct.hf.resume_campaigns or direct.hf.archive_campaigns. The agent must infer usage entirely from the name.

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