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

yandex-marketing-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

yd_bid_modifiers_toggle

Toggle bid modifiers on or off for Yandex Direct campaigns. Specify modifier IDs and set enabled to true or false to control their state.

Instructions

Enable or disable bid modifiers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bid_modifier_ids": "<bid_modifier_ids>",
      "enabled": "<enabled>"
    },
    "name": "yd_bid_modifiers_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bid_modifier_idsYes
enabledYestrue = enable, false = disable
client_loginNoOptional. Override Client-Login for this call (agency multi-account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Without annotations, description should explain side effects, permissions, error handling, or atomicity. Only states action without behavioral context.

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?

Single sentence is concise but lacks structure (e.g., no scoping or constraints). Could be more informative without being verbose.

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?

No output schema or annotations; agent lacks understanding of return value or confirmation of success/failure. Incomplete for a mutation tool with three parameters.

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 descriptions cover 67% of parameters; description adds no extra meaning beyond the schema. The enabled parameter is already documented in schema.

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 clearly indicates the tool enables or disables bid modifiers, distinguishing it from add/delete/get/set siblings. However, 'toggle' is not explicitly defined as flipping the enabled state.

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 tool versus yd_bid_modifiers_set or prerequisites. Agent must infer use case from name alone.

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