Skip to main content
Glama
AppVisionOS

Apple Ads MCP

reports_keywords_in_campaign

Retrieve keyword-level performance metrics aggregated across all ad groups in a campaign. Supports custom date ranges, granularity, and filtering.

Instructions

Keyword report rolled up across all ad groups in one 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 are present, and the description only states it is a 'rolled up' report, failing to disclose behavioral details such as read-only nature, auth requirements, or what happens with empty results.

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?

Single sentence is very concise and immediately understandable, but it omits key information that could be included without much bloat.

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 the tool's complexity (11 parameters, nested objects, no output schema), the description is far too brief. It lacks details on return structure, pagination, filtering, and how to interpret the aggregated data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 64% schema description coverage, the description adds no value beyond the schema. It does not explain important parameters like campaignId, startTime, or the selector object.

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 indicates it provides a keyword report aggregated across all ad groups in a campaign, distinguishing it from per-adgroup or campaign-level reports among siblings.

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

Usage Guidelines3/5

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

No explicit when-to-use or alternatives are provided, but the purpose implies it is for campaign-level keyword metrics. Sibling tool names help infer context.

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