Skip to main content
Glama
askads

VK Ads MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Список групп объявлений

list_ad_groups
Read-onlyIdempotent

Fetch ad groups from VK Ads by IDs, parent campaign, or status. Includes targeting structure and monetary fields in account currency.

Instructions

Возвращает список групп объявлений с необязательной фильтрацией по id, родительской кампании и статусу. Денежные поля — в валюте аккаунта; в targetings лежит структура таргетинга по гео, демографии и интересам.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoФильтр по id групп объявлений.
limitNoСколько объектов на страницу (не больше 250).
fieldsNoПоля группы объявлений в ответе (с «targetings» вернётся полный объект таргетинга).
offsetNoСмещение постраничной выдачи (сколько объектов пропустить).
statusesNoФильтр по статусу.
adPlanIdsNoФильтр по id родительских кампаний.
autoPaginateNoЗабрать все страницы, идя по offset/count (limit при этом не ограничивает общее число объектов).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.0
    • changedInput schema / properties / adPlanIds / description
      Previous value: -"Filter by parent ad plan ids."New value: +"Фильтр по id родительских кампаний."
    • changedInput schema / properties / autoPaginate / description
      Previous value: -"Fetch all pages by following offset/count (ignores limit as a total cap)."New value: +"Забрать все страницы, идя по offset/count (limit при этом не ограничивает общее число объектов)."
    • changedInput schema / properties / fields / description
      Previous value: -"Ad group fields to return (add \"targetings\" for the full targeting object)."New value: +"Поля группы объявлений в ответе (с «targetings» вернётся полный объект таргетинга)."
    • changedInput schema / properties / ids / description
      Previous value: -"Filter by ad group ids."New value: +"Фильтр по id групп объявлений."
    • changedInput schema / properties / limit / description
      Previous value: -"Max objects per page (<=250)."New value: +"Сколько объектов на страницу (не больше 250)."
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset (objects to skip)."New value: +"Смещение постраничной выдачи (сколько объектов пропустить)."
    • changedInput schema / properties / statuses / description
      Previous value: -"Filter by status."New value: +"Фильтр по статусу."
  2. First observedv1.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful semantic behavior beyond that: monetary fields are in account currency, and targetings contains geo/demographic/interest targeting structure. There is no contradiction.

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?

Two concise sentences front-load the core action and filters, then add high-value field semantics about currency and targeting structure. There is no filler or redundant repetition of schema details.

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

Completeness4/5

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

For a read-only list tool with all parameters optional and fully explained by the schema, the description covers the key facts an agent needs: what is returned, available filters, currency behavior, and targetings structure. Pagination details are already in the schema, so their absence from the description is not a gap.

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 all 7 parameters are already documented in the input schema. The description adds context by linking filters to ids, adPlanIds, and statuses and by clarifying the targetings field, but it does not provide syntax or constraints beyond the schema.

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. It clearly distinguishes this read-only listing tool from mutating siblings like create_ad_group, update_ad_group, and ad_group_action, and states the optional filter dimensions.

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

Usage Guidelines4/5

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

The description names the supported filter dimensions (id, parent campaign, status), making the intended use clear. It does not explicitly name alternatives or give when-not-to-use guidance, but the listing context and annotations make the read-only role unambiguous.

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