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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.resume_ads

Resume paused ads in Yandex Direct. Specify ad IDs or a campaign to reactivate them, with dry-run preview and apply options.

Instructions

Human-friendly: resume ads.

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.resume_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
ad_idsNo
dry_runNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
campaign_idNo
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/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 and delivers almost nothing. It implies a state-mutating operation but says nothing about permissions, the role of 'apply' vs 'dry_run', rate limits, or what happens to ads that were never paused.

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

Conciseness2/5

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

It is short, but the brevity reflects under-specification rather than conciseness. The 'Human-friendly:' prefix consumes the front-loaded position with noise instead of the actual action or scope.

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

Completeness1/5

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

For a 7-parameter mutation tool with no annotations and no output schema, the definition is far too thin. The un-annotated dry-run/apply workflow and the ad-targeting parameters are entirely undocumented, leaving an agent unable to call it safely.

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

Parameters1/5

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

Schema description coverage is only 29% across 7 parameters, and the description adds zero parameter meaning. Critical controls like 'apply', 'dry_run', and 'ad_ids' are left entirely unexplained in both the schema and the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'resume ads' names a recognizable verb+resource, so the basic action is inferable. However, the 'Human-friendly:' prefix is filler and the description does nothing to distinguish this from near-identical siblings such as direct.hf.pause_ads, direct.hf.unarchive_ads, or direct.hf.archive_ads.

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?

There is no guidance on when to use this tool versus the many sibling ad-state tools. An agent gets no signal about prerequisites (e.g. whether ads must be paused/archived first) or what conditions select this over archive/unarchive variants.

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