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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.list_bidmodifiers

Retrieve bid modifiers for Yandex Direct campaigns with pagination, field selection, and optional filters. Use it to inspect campaign-level bid adjustments before updating or auditing them.

Instructions

List bid modifiers.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPagination: {"limit": int, "offset": int}.
paramsNoRaw Direct params override (advanced).
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
field_namesNoBid modifier field names (default: CampaignId).
selection_criteriaNoDirect API SelectionCriteria object (optional).
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.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing beyond the bare purpose. 'List' weakly implies a read-only, non-destructive operation, but there is no information about account/Client-Login requirements, pagination behavior, rate limits, or return shape.

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 single sentence is front-loaded and contains no waste, but its brevity reflects under-specification rather than effective concision. A four-word description for a six-parameter tool with nested objects leaves essential context unstated.

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?

The tool takes six parameters including nested objects (page, selection_criteria, params), has no annotations, no output schema, and no required fields, so the description is the only source of behavioral context — and it provides none. An agent cannot tell from this text how to scope the listing or what Direct account context is needed.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (account_id, field_names, direct_client_login, selection_criteria, page, params) is already documented in the schema, setting the baseline at 3. The description adds no syntax, defaults, or meaning beyond what the schema supplies.

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 and resource ('List bid modifiers'), so the operation is unambiguous. However, it offers no differentiation from closely related siblings such as direct.list_bids, direct.list_bidmodifiers-style tools, or direct.hf.clear_bid_modifiers, leaving the agent to infer scope from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives, despite many sibling list/set tools existing in the direct.* family. The agent must guess when this tool is preferable to direct.list_bids or the direct.hf.set_bid_modifier_* tools.

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