Retrieves the Apple Ads account ACLs available to a specified profile so you can identify which accounts are accessible before running reports or audits.
Discover Apple Ads account ACLs available to a profile.
| Name | Required | Description | Default |
|---|---|---|---|
| profile | Yes | local Apple Ads profile name |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | payload | |
| error | No | ||
| summary | Yes | ||
| rateLimit | No | ||
| pagination | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds that results are ACLs available to a profile, but does not add further behavioral context such as pagination, rate limits, or permission requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. The scoping condition (available to a profile) is stated immediately and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity list tool with full schema coverage, rich annotations, and an output schema, the description is largely complete. The main remaining gap is routing guidance against related account-listing and account-getting siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single profile parameter is already documented as a local Apple Ads profile name. The description reinforces that the profile scopes the result to available ACLs, but adds no syntax or format detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb (Discover) and a precise resource (Apple Ads account ACLs) scoped to a profile. It is clearly a list/discovery operation, but it does not explicitly differentiate itself from siblings like ad_account_get or advertiser_resources_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies the tool is used with a profile, but does not state when to use it versus alternatives such as ad_account_get or advertiser_resources_list. There are no exclusions or prerequisite guidance beyond the required profile parameter already in the schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.