Skip to main content
Glama
Qusto

vk-ads-mcp

by Qusto

list_banners

Read-onlyIdempotent

Retrieve all banners (creatives) from your VK Ads cabinet. Supports filtering by ad group, status, and field selection for rich creative data including content and moderation status.

Instructions

List banners (creatives) in the own VK Ads cabinet.

Fetches every banner from GET /banners.json, transparently paginating over all result pages, and returns the RAW item dicts so every requested field reaches you for analysis. Read-only.

By default the API returns a MINIMAL field set. Pass fields to get rich creative data, e.g. "id,status,content,textblocks,urls,moderation_status". The content field carries the creative variants/urls. Call the describe_fields tool with resource="banners" first to learn the full set of valid field names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_group_idNoRestrict results to banners belonging to this ad group. Mapped to the API filter ``_ad_group_id__in``.
fieldsNoOptional comma-separated list of fields to request from the API. Forwarded verbatim as the ``fields`` param. Rich fields include ``content``, ``textblocks``, ``urls``, ``moderation_status`` — see ``describe_fields``.
statusNoRestrict results to banners with this status (e.g. ``active``, ``blocked``). Mapped to the API filter ``_status__in``.
sortingNoOptional sort spec, e.g. ``"-id"`` or ``"id"``. Forwarded verbatim as the ``sorting`` query parameter.
limitNoPage size for pagination (1-50). The API caps page size at 50; larger values are clamped. This affects request batching only — all matching banners are returned regardless.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds valuable behavioral details: transparent pagination, returning raw item dicts, default minimal field set, and the effect of the 'fields' parameter. No contradiction with annotations.

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 four sentences, front-loaded with purpose, and every sentence adds value—pagination, read-only, field selection, and a pointer to describe_fields. No redundancy or filler.

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 the existence of an output schema and annotations, the description covers all needed context: what the tool does, pagination behavior, read-only nature, parameter usage tips, and how to explore fields. It is self-contained and sufficient for correct invocation.

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?

Schema coverage is 100%, providing baseline 3. The description adds meaning beyond schema with examples (e.g., 'content' field carries variants/urls) and behavioral notes (limit clamping, all banners returned). This incremental value justifies a score of 4.

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 'List banners (creatives) in the own VK Ads cabinet.' with a specific verb and resource. Although it does not explicitly contrast with sibling tools, the resource 'banners' is distinct from 'ad_groups' or 'campaigns' in sibling names, making it unambiguous.

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 provides clear context on how to use the tool, including parameter guidance (e.g., pass 'fields' for rich data) and a recommendation to call 'describe_fields' first. It lacks explicit when-not-to-use or alternatives, but the context is sufficient.

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/Qusto/vk-ads-mcp'

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