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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.set_adgroup_autotargeting

Enable or disable autotargeting for a Yandex Direct ad group, with dry-run preview and best-effort support depending on campaign type.

Instructions

Human-friendly: enable/disable autotargeting (best effort, depends on campaign type).

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

Input Schema

NameRequiredDescriptionDefault
applyNo
dry_runNo
enabledNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
adgroup_idNo
campaign_idNo
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.9/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 burden; it does disclose a real behavioral trait — that the operation is best-effort and campaign-type dependent, so it can silently no-op. But it says nothing about required permissions, whether the change is reversible, the side effects of disabling autotargeting on existing keywords, or the dry_run/apply mechanics.

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 front-loaded sentence with no filler; the caveat is placed inline rather than buried. It is efficient, though it trades away detail that this 7-parameter mutation tool needs.

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?

This is a mutation tool with no annotations, no output schema, and 71% of parameters undocumented, yet the description covers only the headline action. The apply/dry_run preview-vs-commit behavior and the target identifiers essential for correct invocation are entirely unaddressed.

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 description coverage is only 29% (2 of 7 params), and the description adds no parameter meaning at all. Five parameters — apply, dry_run, enabled, adgroup_id, campaign_id — are undocumented in both schema and description, so an agent must guess at the boolean control semantics.

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 (enable/disable) and resource (autotargeting) scoped to an adgroup, which distinguishes it from the sibling direct.hf.set_autotargeting_bid. It does not, however, mention which identifiers select the target adgroup, leaving part of the 'what' implicit.

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 guidance on when to use this versus set_autotargeting_bid or update_adgroups, no prerequisites, and no mention of the dry_run/apply workflow. The phrase 'best effort, depends on campaign type' hints that it may not apply universally but never says what to do instead.

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