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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.set_bid_modifier_mobile

Set the mobile bid modifier percent for a Yandex Direct campaign to adjust mobile ad bids. Supports dry runs and account-level overrides.

Instructions

Human-friendly: set mobile bid modifier (percent).

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

Input Schema

NameRequiredDescriptionDefault
applyNo
dry_runNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
campaign_idNo
campaign_nameNo
value_percentNo
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.2/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 burden of behavioral disclosure. It implies a write/mutation operation and specifies the percent unit, but says nothing about permissions, side effects, reversibility, apply/dry_run semantics, or required targeting parameters.

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?

The single sentence is short, but it is under-specified rather than concise. The 'Human-friendly:' prefix is filler that does not earn its place, and the sentence omits essential structure about scope and required inputs.

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, no output schema, and low schema coverage, the description is critically incomplete. An agent cannot determine required inputs, the effect of apply/dry_run, or how mobile bid modifiers are targeted from this description alone.

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 low at 29%, so the description should compensate for undocumented parameters. It only clarifies that value_percent is a percent for mobile bid modification; it does not explain apply, dry_run, campaign_id, or campaign_name, leaving most parameters ambiguous.

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 names a specific verb and resource (set mobile bid modifier) and identifies the unit (percent), which distinguishes it from sibling tools such as set_bid_modifier_desktop and set_bid_modifier_demographics. However, the preamble 'Human-friendly' adds no discriminative meaning, and the scope (campaign/adgroup level) is not stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 alternatives like set_bid_modifier_desktop, set_bid_modifier_geo, or clear_bid_modifiers. No prerequisites, exclusions, or context for invocation are provided.

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