Apple Ads MCP

cpp_locale_details

Retrieve locales available for a Custom Product Page, showing localized assets for each locale.

Instructions

List the locales available for a Custom Product Page (with localized assets per locale).

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>",
      "productPageId": "<productPageId>"
    },
    "name": "cpp_locale_details"
  }
}

Input Schema

Name	Required	Description
`adamId`	Yes
`productPageId`	Yes
`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.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral transparency. It indicates a read operation (list) but does not disclose any side effects, authentication requirements, or scope of data returned (e.g., pagination, format). For a listing tool, this is minimal disclosure.

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 that is clear and front-loaded with the purpose. It is concise but could benefit from a brief note on usage context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three parameters (two required) and no output schema. The description covers the high-level purpose but does not explain the return format or what 'localized assets' means. Given the simplicity, it is minimally adequate but lacks depth for a complete understanding.

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?

Schema description coverage is low (33%, only for `orgId`). The description does not explain `adamId` or `productPageId`, which are required. The `orgId` parameter has a schema description, but the description adds no additional 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 tool's action ('List the locales available for a Custom Product Page') and includes contextual detail ('with localized assets per locale'). It distinguishes itself from siblings like `cpp_get` and `apps_locale_details` by specifying 'Custom Product Page' and 'locales'.

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 guidance on when to use this tool vs. alternatives. The description implies usage when needing locales for a specific CPP, but it does not mention `apps_locale_details` or other `cpp_*` tools. The context is clear but lacks exclusions.

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

Deploy Server