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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.set_adgroup_tracking_params

Sets tracking parameters for an ad group; use dry-run to preview and apply to save changes.

Instructions

Human-friendly: set TrackingParams for an ad group.

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_tracking_params"
  }
}

Input Schema

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation via 'set' but does not explain permissions, whether changes affect existing ads, how apply/dry_run behave, or what the operation returns.

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?

The description is a single short sentence and is front-loaded, which is good. However, the phrase 'Human-friendly:' adds no useful meaning for an agent, and the extreme brevity leaves necessary operational context missing.

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 six-parameter mutation tool with no annotations and no output schema, the description is far too sparse. It does not cover the apply/dry_run workflow or identifier semantics, which an agent would need before invoking it safely.

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 33%, leaving apply, dry_run, adgroup_id, and tracking_params without schema descriptions. The description vaguely references tracking params but does not explain the format, required identifiers, or the important apply/dry_run controls.

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 ('set') and resource ('TrackingParams for an ad group'), so the core operation is clear. It distinguishes this tool from the campaign-level sibling direct.hf.set_campaign_tracking_params by scope, though it does not explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus direct.hf.set_campaign_tracking_params, direct.hf.apply_utm_to_ads, or other tracking-related siblings. It also does not mention prerequisites, dry-run workflows, or when not to use it.

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