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

yandex-direct-mcp

by artgas1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

campaigns.get

direct_campaigns_get
Read-onlyIdempotent

Retrieve Yandex Direct campaign parameters by IDs, types, states, or statuses. Select specific fields like budgets, settings, and bidding strategies to analyze or manage campaigns.

Instructions

Возвращает параметры кампаний, отвечающих заданным критериям.

Служба campaigns, метод get (чтение). Документация: https://yandex.ru/dev/direct/doc/ru/campaigns/get

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": {
      "FieldNames": "<FieldNames>"
    },
    "name": "direct_campaigns_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
PageNoобъект LimitOffset: Limit, Offset (точная схема: direct_schema с type=LimitOffset)
FieldNamesYes22 значений (BlockedIps, ExcludedSites, Currency, DailyBudget, …) — полный список: direct_fields
SelectionCriteriaNoобъект CampaignsSelectionCriteria: Ids, Types, States, Statuses, StatusesPayment (точная схема: direct_schema с type=CampaignsSelectionCriteria)
TextCampaignFieldNamesNo11 значений (CounterIds, RelevantKeywords, Settings, BiddingStrategy, …) — полный список: direct_fields
SmartCampaignFieldNamesNoодно из: CounterId, Settings, BiddingStrategy, PriorityGoals, TrackingParams, AttributionModel, PackageBiddingStrategy, CanBeUsedAsPackageBiddingStrategySource
UnifiedCampaignFieldNamesNo10 значений (CounterIds, Settings, BiddingStrategy, PriorityGoals, …) — полный список: direct_fields
CpmBannerCampaignFieldNamesNoодно из: CounterIds, FrequencyCap, VideoTarget, Settings, BiddingStrategy
MobileAppCampaignFieldNamesNoодно из: Settings, BiddingStrategy, PackageBiddingStrategy, CanBeUsedAsPackageBiddingStrategySource, NegativeKeywordSharedSetIds, WeeklyBudgetRollover
DynamicTextCampaignFieldNamesNo10 значений (PlacementTypes, CounterIds, Settings, BiddingStrategy, …) — полный список: direct_fields
TextCampaignSearchStrategyPlacementTypesFieldNamesNoодно из: SearchResults, ProductGallery, DynamicPlaces
UnifiedCampaignSearchStrategyPlacementTypesFieldNamesNoодно из: SearchResults, ProductGallery, DynamicPlaces, Maps, SearchOrganizationList
UnifiedCampaignPackageBiddingStrategyPlatformsFieldNamesNoодно из: SearchResult, ProductGallery, Maps, SearchOrganizationList, Network, DynamicPlaces
DynamicTextCampaignSearchStrategyPlacementTypesFieldNamesNoодно из: SearchResults, ProductGallery, DynamicPlaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'чтение' (read), which is redundant but consistent. No additional behavioral context (e.g., pagination, auth, rate limits) is provided, but the annotation coverage warrants a baseline score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences with the primary action front-loaded, plus a documentation link. There is no filler or redundant information beyond the necessary context.

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?

With 13 parameters, nested objects, and no output schema, the description is inadequate. It does not explain the overall request/response flow, that FieldNames is required to select fields, or how pagination via the Page object works. While the schema descriptions provide per-parameter detail, the high-level description leaves out essential usage context for an agent to call this tool 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 description coverage is 100%—every parameter has a detailed description listing allowed values and references to direct_fields. The tool description itself adds no parameter-specific information beyond the general purpose, so it does not exceed the baseline.

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 states it returns campaign parameters matching criteria, with the verb 'Возвращает' (returns) and resource 'кампаний' (campaigns). The resource is unambiguous and distinct from sibling tools like direct_ads_get or direct_adgroups_get, though it doesn't 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?

There is no guidance on when to use this tool versus alternatives such as direct_ads_get or direct_keywords_get. The description only states what it does, not the context or prerequisites. The documentation link is a resource but not inline guidance.

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