Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

create_custom_report

Create a custom report by selecting report type, date range, grouping period, columns, and filters to retrieve specific advertising performance data.

Instructions

Create a new report configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate configuration (either preset or start+end required)
nameYesReport name
typeYesReport type
periodYesData grouping period
columnsNoColumns to include: impressions, eligible, viewable, clicks, conversions, ctr, cvr, e_cpm, e_cpc, e_cpa, cost, payout, revenue
filtersNoFilter criteria: { publishers: [...], advertisers: [...], zones: [...], campaigns: [...], ad_items: [...], channels: [...] }
exclude_channel_statsNoExclude stats from channel-served ads
require_channel_statsNoOnly include stats from channel-served ads
exclude_campaign_ad_itemsNoExclude ad items in campaigns
exclude_publisher_ad_itemsNoExclude ad items directly in zones
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits, but it only says 'Create a new report configuration'. It does not explain whether this triggers report generation, how it relates to scheduled reports, what the persisted configuration looks like, or any side effects or permissions needed.

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

Conciseness3/5

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

The description is a single, front-loaded sentence with no wasted words. However, for a tool with 10 parameters and nested objects, this brevity borders on under-specification rather than effective conciseness.

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

Completeness1/5

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

Given the tool's complexity (10 parameters, nested objects, no output schema, no annotations), the one-sentence description is woefully incomplete. It fails to explain return values, execution behavior, naming conventions, or the difference between creating a report configuration versus generating a report.

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 input schema has 100% coverage with descriptions for all parameters, including nested fields like 'date'. The description itself adds no parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 the verb 'Create' and the resource 'report configuration', which conveys the core purpose. However, it does not distinguish this from the sibling tool 'create_vast_custom_report' or clarify whether this is for display reports versus VAST reports.

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 is provided on when to use this tool versus alternatives like 'create_report_schedule' or 'create_vast_custom_report'. The description only states the action, leaving the agent to infer usage context from the name.

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

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