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

yandex-direct-mcp-plus

by Pavelsiba

Список групп

list_ad_groups
Read-only

Retrieves ad groups for specified Yandex.Direct campaigns, returning names, regions, and statuses by default; specify fields to include negative keywords, tracking parameters, or serving status.

Instructions

Группы объявлений выбранных кампаний: названия, регионы, статусы. По умолчанию возвращается узкий набор полей; нужны другие (NegativeKeywords, NegativeKeywordSharedSetIds, TrackingParams, ServingStatus и прочие из AdGroupFieldEnum) — перечислите их в fields.

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_ids": "<campaign_ids>"
    },
    "name": "list_ad_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
fieldsNoКакие поля вернуть; по умолчанию Id, Name, CampaignId, RegionIds, Status, Type
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
campaign_idsYesКампании, группы которых нужно выбрать

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Какие поля вернуть; по умолчанию Id, Name, CampaignId, RegionIds, Status, Type",
      +  "items": {
      +    "enum": [
      +      "CampaignId",
      +      "Id",
      +      "Name",
      +      "NegativeKeywordSharedSetIds",
      +      "NegativeKeywords",
      +      "RegionIds",
      +      "RestrictedRegionIds",
      +      "ServingStatus",
      +      "Status",
      +      "Subtype",
      +      "TrackingParams",
      +      "Type"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. First observedv1.6.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral fact beyond the annotations — that only a narrow default field set is returned unless fields is supplied — but says nothing about result ordering, pagination behavior, or volume limits for large campaign sets.

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?

Two short sentences, front-loaded with what is returned, then the fields escape hatch. Efficient, though the second sentence duplicates the schema's default-field note rather than adding new information.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and no output schema, the description is adequate but incomplete on the return side: it never says the response is a paginated collection keyed off 'LimitedBy' (only hinted at by the offset parameter), nor how default fields interact with typed returns.

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%, so campaign_ids, fields, limit and offset are already documented in the schema. The description largely restates the schema's default field list ('Id, Name, CampaignId, RegionIds, Status, Type') and only adds the AdGroupFieldEnum name and a few example extended fields, so the marginal value is limited.

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+resource (listing ad groups) scoped to selected campaigns and enumerates the default returned attributes (names, regions, statuses). It is clearly distinguishable from list_campaigns and from the mutating siblings create_ad_group/update_ad_group/delete_ad_groups, though it never names a sibling explicitly.

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?

Usage is only implied: it presumes the caller already has campaign_ids and wants their ad groups. There is no stated when-to-use vs. alternatives, no prerequisite/permission notes, and no guidance on pagination or when to prefer a more targeted tool.

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