Apple Ads MCP

creatives_find

Search for creatives across your Apple Ads organization using a selector with conditions, fields, sorting, and pagination.

Instructions

Find creatives across the org with a selector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "creatives_find"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes	Selector object for /find endpoints. Combine conditions / fields / orderBy / pagination.
`orgId`	No	Override 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.

First observedv0.1.0May 3, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present, so the description must convey behavioral traits. It only states 'Find' which implies read-only, but does not explicitly confirm non-destructiveness, discuss permissions, pagination behavior beyond schema, or error conditions. The agent cannot infer safety or side effects.

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 sentence, which is concise but may be too brief. It front-loads the action and scope, but omits important context. It earns its place but could be expanded slightly to improve completeness without becoming verbose.

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 complexity of nested parameters, multiple sibling find tools, and lack of output schema, the description is incomplete. It does not clarify how the selector works at a high level, what 'across the org' entails, or how it differs from other find tools. The agent cannot fully understand the tool's role.

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% (both parameters have descriptions), so the tool description does not need to add much. It adds no further semantics beyond the schema. The selector object's description in the schema covers its role adequately.

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 action ('Find'), the resource ('creatives'), and the scope ('across the org'). It distinguishes from list tools by mentioning a selector, but does not explicitly contrast with other find tools (e.g., adgroups_find_org_wide), though the resource name provides differentiation.

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_list, creatives_get, or other find tools. The description fails to mention prerequisites, scenarios, or trade-offs, leaving the agent without decision context.

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

Deploy Server