Skip to main content
Glama
AppVisionOS

Apple Ads MCP

reports_adgroups

Generate ad-group-level performance reports for a campaign with flexible time ranges, granularity, filtering, and pivoting options.

Instructions

Ad-group-level report within a single campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYes
startTimeYesInclusive start. Format YYYY-MM-DD for DAILY/WEEKLY/MONTHLY, or ISO 8601 datetime for HOURLY.
endTimeYesInclusive end.
granularityNoDefaults to none (single aggregated row per entity).
timeZoneNoORTZ = the org's reporting timezone.
selectorNoSelector controlling sort, filtering, and pagination of the report rows.
groupByNoPivot the report along these dimensions.
returnRecordsWithNoMetricsNo
returnRowTotalsNo
returnGrandTotalsNo
orgIdNoOverride the org (account) for this call. Defaults to ASA_ORG_ID. Use the `org_acls` tool to discover orgIds.
Behavior2/5

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

No annotations provided and description does not disclose behavioral traits such as rate limits, authentication requirements, or side effects. Only states what the tool does.

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?

Very concise single sentence, but lacks context that could be included without losing conciseness. Adequate but minimal.

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?

Description is grossly incomplete for a complex tool with 11 parameters, nested objects, and no output schema. Does not explain return values, constraints, or how to effectively use the 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?

Schema description coverage is high (64%), so baseline is 3. Description adds no additional parameter meaning beyond what the schema provides.

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?

Description clearly states it is an ad-group-level report within a single campaign, using specific verb and resource. It differentiates from siblings like reports_campaigns and reports_ads_in_campaign.

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 alternatives. Lack of explicit when-to-use or when-not-to-use instructions amidst many sibling report tools.

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/AppVisionOS/apple-search-ads-mcp'

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