Skip to main content
Glama

List ad campaigns

list_campaigns
Read-onlyIdempotent

Fetch a paginated list of ad campaigns with filters for status, type, dates, and managers. Also returns weekly API point balance.

Instructions

Lists the account's ad campaigns, one page at a time. Returns {total, items, page, limit, hasNextPage} plus apiPointBalance — the weekly API points left, which refill Mondays 00:00 UTC. Each campaign carries id, name, status, budget (rubles), paymentModel (CPM/CPC), campaignType, startDate/endDate, advertiserId, contractId, managerID and timestamps. All filter fields are AND-ed and each list keeps only the values it names. This API cannot create, edit, pause, resume, archive or delete a campaign and cannot touch its targeting — the only writes available anywhere are change_group_budget and change_group_price on an ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoCampaign ids to keep.
pageNo1-based page number. Default 1.
limitNoPage size, 1..100. Default 20.
filterNoEscape hatch: extra filter keys merged as-is into the request filter (API spelling). The named fields above win on conflict.
managersNoManager (account user) ids whose campaigns to keep.
statusesNoCampaign statuses to keep: draft, in_moderation, moderation_failed, partial_moderation, active, paused, stopped, finished, archived.
createdAtNoKeep campaigns created in this range: {from, to}, YYYY-MM-DD.
timeFrameNoKeep campaigns whose flight window falls in this range: {from, to}, YYYY-MM-DD.
advertisersNoAdvertiser ids whose campaigns to keep.
contractIdsNoContract ids whose campaigns to keep.
campaignTypesNoCampaign types to keep: textImage, HTML, video.
paymentModelsNoPayment models to keep: CPM, CPC.
additionalAgreementIdsNoAdditional-agreement ids whose campaigns to keep.
Behavior4/5

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

Beyond annotations, the description adds paging mechanics, response shape including apiPointBalance and refill schedule, filter AND-ing semantics, and a clear no-write boundary. The statement that change_group_budget and change_group_price are 'the only writes available anywhere' is slightly misleading given other write tools in the sibling list, which prevents a perfect 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 packed with useful information in a logical order: purpose, output shape, field list, filter behavior, and limitations. Every sentence earns its place, and the length is justified by the tool's complexity.

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?

Given 13 parameters, nested objects, and no output schema, the description thoroughly covers return value structure, pagination, filter logic, and mutation limitations. It is complete enough for an agent to invoke the tool correctly without additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds meaning by explaining that all filter fields are AND-ed and that each list parameter keeps only the values it names, clarifying how the 13 parameters interact. This goes beyond the schema descriptions.

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 clearly states 'Lists the account's ad campaigns, one page at a time,' which specifies a concrete verb and resource. It distinguishes this tool from sibling list tools by focusing on campaigns and pagination behavior.

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 explicitly says the tool cannot create/edit/pause/resume/archive/delete campaigns or touch targeting, providing clear when-not guidance. It also names change_group_budget and change_group_price as the only write alternatives, though the 'anywhere' phrasing overstates their scope. No explicit comparison to related list/stats tools is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/A1-x-Tech/mcp-avito-ads'

If you have feedback or need assistance with the MCP directory API, please join our Discord server