Skip to main content
Glama
Qusto

vk-ads-mcp

by Qusto

get_statistics

Read-onlyIdempotent

Fetch performance statistics for VK Ads objects, automatically splitting large date ranges and ID lists to comply with API limits.

Instructions

Fetch performance statistics for VK Ads objects.

Retrieves statistics from GET /statistics/{object_type}/{period}.json and returns a merged {"items": [...]} payload. The underlying client transparently handles the API's hard limits: date ranges longer than 92 days are split into multiple inclusive windows, and id lists longer than 50 are chunked, with all responses merged into a single result. The caller never has to worry about those limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYesThe object level to report on. One of: * ``"ad_plans"`` — campaign-level statistics. * ``"ad_groups"`` — ad-group-level statistics. * ``"banners"`` — banner (creative) level statistics.
date_fromNoInclusive start date in ``YYYY-MM-DD`` format (e.g. ``"2025-01-01"``). When omitted the API applies its own default window. Mostly relevant for ``period="day"``.
date_toNoInclusive end date in ``YYYY-MM-DD`` format (e.g. ``"2025-01-31"``). Must not precede ``date_from``. When omitted the API applies its own default window.
periodNoThe aggregation period. One of: * ``"day"`` (default) — one row per day in the date range; use this for time-series breakdowns. * ``"summary"`` — a single aggregated total over the whole range.day
idsNoOptional list of object ids to restrict the report to (campaign, ad-group or banner ids matching ``object_type``). When omitted, statistics are returned for all objects of that type.
metricsNoThe metrics group to include. One of: * ``"base"`` (default) — core delivery metrics (shows, clicks, spent, CTR, CPC, CPM, etc.). * ``"all"`` — every available metric group. * ``"uniques"`` — reach / unique-users metrics. * ``"video"`` — video-specific metrics (views, view depth, etc.).base

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description adds significant value beyond annotations by revealing that the client transparently splits date ranges over 92 days and chunks id lists over 50, merging results. This discloses behavior not evident from readOnlyHint and idempotentHint alone.

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 concise at 5 sentences, front-loaded with a clear purpose, and uses efficient language. Every sentence adds value without repetition.

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 tool complexity (6 parameters, 1 required) and presence of an output schema, the description fully covers purpose, behavior, and parameter-related constraints. No gaps remain.

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%, but the description adds context about how parameters relate to API limits (e.g., date_from/date_to splitting, ids chunking), providing meaning 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 'Fetch performance statistics for VK Ads objects' and explains the API endpoint. It distinguishes this tool from siblings like 'get_top_objects' or 'list_campaigns' by focusing on statistics.

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 for when to use this tool (retrieving statistics) and explains that the client handles API limits automatically. However, it does not explicitly compare to alternatives or state when not to use it.

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