Apple Ads MCP

apps_assets_find

Retrieve App Store screenshots and app preview assets for an app. Returns assetGenIds for creative authoring or auditing rejected assets.

Instructions

Find App Store screenshots / app-preview assets for an app — returns assetGenIds you can use to author creatives or audit rejected assets.

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": {
      "adamId": "<adamId>",
      "selector": "<selector>"
    },
    "name": "apps_assets_find"
  }
}

Input Schema

Name	Required	Description
`adamId`	Yes
`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

B3.4/5.0

Behavior2/5

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

No annotations provided; description only states function and output, missing details on auth, rate limits, or failure behavior.

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

Conciseness5/5

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

Single sentence, front-loaded with key information, no filler.

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?

Despite complexity (nested selector, no output schema), description omits guidance on crafting selector or typical use cases, leaving gaps.

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?

Description adds meaning about return use (assetGenIds for creatives/rejected assets), but parameters (adamId, selector, orgId) are not explained beyond schema's own descriptions.

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 finds App Store screenshots/app-preview assets for an app and returns assetGenIds for creatives or auditing, distinct from sibling tools targeting other entities.

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?

Provides usage context (authoring creatives, auditing rejected assets) but no explicit when-to-use vs alternatives like creatives_find or apps_get.

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

Deploy Server