Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

Кампания по ID

get_campaign
Read-only

Retrieve detailed advertising campaign data by ID, including budget, status, dates, statistics, UTM tags, goals, Metrica counters, attribution model, and settings.

Instructions

Детальная информация о кампании по ID: бюджет (руб), статус и пояснение к нему, даты, статистика, UTM-разметка, цели и их ценность (PriorityGoals), счётчики Метрики, модель атрибуции и прочие настройки. Реальные ID целей — PriorityGoals.Items[].GoalId; GoalId 13 в стратегии — служебное «ключевые цели», то есть оптимизация по этим PriorityGoals. Пустой ответ по ID из веб-интерфейса не значит, что номер неверный: кампании «Баннер на поиске» (MCBANNER) API не отдаёт, по ID они приходят пустыми.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesID рекламной кампании, десятичная строка

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.6.1

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare a read-only, open-world lookup, so the description earns credit for adding behavior the annotations cannot: an empty response is a legitimate outcome for MCBANNER ('Баннер на поиске') campaigns rather than a bad ID. That single sentence prevents a wrong retry loop. It does not, however, describe pagination or the shape of the statistics block.

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?

The purpose is front-loaded and the field enumeration is dense but useful. The PriorityGoals/GoalId 13 digression is jargon-heavy and only partially relevant to fetching a campaign, but it does preempt a real misreading of returned data, so it earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must characterize the return value, and it does so by listing the returned sections plus the PriorityGoals.Items[].GoalId structure. Combined with the empty-response caveat, an agent has everything needed to call and interpret the result correctly.

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 coverage is 100% and the single campaign_id parameter already carries a format description and numeric pattern, so the schema does the work. The description adds nothing further about the parameter itself — the empty-response note concerns output, not the ID format — making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Детальная информация о кампании по ID' — and then enumerates exactly what detail is meant (budget, status, dates, statistics, UTM, goals, counters, attribution). An agent can immediately distinguish this single-campaign lookup from the sibling list_campaigns.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied by 'по ID' but never stated explicitly: there is no guidance on where to obtain the ID (e.g., from list_campaigns) or on when to prefer this over a statistics call. The MCBANNER caveat is a valuable retrieval warning, but it addresses result interpretation rather than tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.