Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_get_stats

Read-only

Retrieve advertiser statistics with support for custom reports, per-site analytics, and conversion logs, using flexible metrics and groupings.

Instructions

Advertiser statistics. reportType: 'custom' (default, report builder), 'sites' (per-site), or 'conversions' (event log). For custom reports use names like 'spend,clicks,ctr' (metrics) and 'day,campaign,country' (groupBy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportTypeNocustom
periodNo7days
dateFromNo
dateToNo
pageNo
perPageNo
sortByNo
sortOrderNo
groupByNoComma-separated groupings, e.g. 'day,campaign,country' (incl. campaign_group). Unknown names are reported back.
metricsNoComma-separated metric names, e.g. 'spend,clicks,ctr,cpa,conversions,income,roi' (income = profit). Unknown names are reported back; see report-dimensions for the full list.spend,clicks,impressions,ctr
campaignIdsNo
countriesNo
creativeIdsNo
viewNoall
searchQueryNo
conversionTypesNoComma-separated conversion type IDs (for reportType=conversions)
folderIdsNoComma-separated campaign group (folder) IDs (for reportType=conversions)
audienceIdsNoComma-separated audience IDs (for reportType=conversions)
timezoneNoTimezone offset in hours (for reportType=conversions)
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description aligns with a read operation. The description adds value by explaining report types and parameter details, but lacks disclosure on pagination, error handling, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short sentences and a fragment, front-loading the purpose. It efficiently introduces key options without extra verbiage.

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

Completeness2/5

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

Given 19 parameters and no output schema, the description is insufficient. It omits return value format, pagination behavior, and how to interpret responses, leaving significant gaps for an AI agent.

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?

The description adds meaning by explaining reportType options and providing examples for metrics and groupBy, partially compensating for the low schema description coverage (32%). However, many parameters remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Advertiser statistics' and explains the three report types with examples for metrics and groupBy. It distinguishes itself from sibling CRUD and list tools by focusing on statistical data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like list_campaigns or other read tools. It does not mention alternatives or conditions for use.

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/kadam-official/mcp-server'

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