list_campaigns
Retrieve all ad campaigns from your VK Ads cabinet with optional field selection, status filtering, and sorting. Handles pagination automatically to return complete results.
Instructions
List ad campaigns (VK Ads ad_plans) for the authenticated cabinet.
Fetches every campaign from GET /ad_plans.json, transparently walking
the offset-based pagination, and returns the RAW item dicts so every field
you request reaches you for analysis.
By default the API returns a MINIMAL field set. To get rich data pass
fields with the columns you need, e.g.
"id,name,status,objective,budget_limit,budget_limit_day,autobidding_mode,"
"max_price,priced_goal,delivery,efficiency_status,date_start,date_end".
Call the describe_fields tool with resource="ad_plans" first to learn
the full set of valid field names for this resource.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Optional comma-separated list of object fields to request from the API. Forwarded verbatim as the ``fields`` query parameter. When ``None`` the API default (minimal) field set is returned. Rich fields include ``objective``, ``budget_limit_day``, ``autobidding_mode``, ``priced_goal``, ``delivery``, ``efficiency_status`` — see ``describe_fields``. | |
| status | No | Optional campaign status to filter by (sent as the ``_status__in`` filter), e.g. ``"active"``, ``"blocked"``, ``"deleted"``. When ``None`` no status filter is applied. | |
| sorting | No | Optional sort spec, e.g. ``"-id"`` (newest first) or ``"id"``. Forwarded verbatim as the ``sorting`` query parameter. | |
| limit | No | Page size for pagination (1-50). The API caps page size at 50; larger values are clamped. This affects request batching only — all matching campaigns are returned regardless. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |