Skip to main content
Glama
Sign In
Apple Ads MCP

Apple Ads MCP

by AppVisionOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

creatives_list

Retrieve a paginated list of all creatives in an Apple Ads account. Use limit and offset to manage result size.

Instructions

List all creatives in the org (paginated).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "creatives_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page. Apple's hard cap is 1000 for most endpoints.
offsetNoResult offset for pagination.
orgIdNoOverride the org (account) for this call. Defaults to ASA_ORG_ID. Use the `org_acls` tool to discover orgIds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions pagination but lacks details on ordering, filtering, rate limits, authentication requirements, or that the operation is read-only.

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 a single sentence with no wasted words. It is appropriately concise, though front-loading the scope and pagination could be slightly improved.

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 no output schema, the description should inform about return format or fields. However, it only states pagination, leaving the agent unaware of the response structure. The 3 parameters are all optional, which is fine, but completeness is lacking.

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 100%, so the baseline is 3. The description adds 'paginated' context, but the schema already documents limit, offset, and orgId adequately. No extra meaning beyond the schema.

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 the action 'List', the resource 'creatives', and the scope 'in the org', with an explicit pagination note. This distinguishes it from sibling tools like 'creatives_find' and 'creatives_get'.

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 'creatives_find' for filtered searches. No exclusions or context for selection are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools