MCP Apple Ads

Apple Ads: Suggest Keywords

apple_ads_suggest_keywords

Read-only

Generate Apple keyword suggestions from an app ID or seed term to plan campaigns before creating keywords, then pair with search-term reports to see which real searches already reach you.

Instructions

Ask Apple for keyword suggestions for an app or a seed term. The research tool: use it before creating keywords, and pair it with apple_ads_get_report at level "search_term" to see which real searches already reach you.

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

Input Schema

Name	Required	Description
`limit`	No	How many records to return (1-1000). Apple's own maximum page size is 5000.
`adamId`	Yes	The App Store app id to suggest keywords for.
`savePath`	No	Absolute path to also write this result to, as pretty-printed JSON. Use it rather than copying values out of the response into a file by hand. Parent directories are created.
`adAccountId`	No	The ad account to act on. Omit it when you have exactly one or APPLE_ADS_AD_ACCOUNT_ID is set — it is resolved automatically. List them with apple_ads_list_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds useful framing as a research step plus the downstream reporting pair. It says nothing about latency, Apple-side rate limits, result volume relative to the limit parameter, or the shape of the returned suggestions, so the extra value is modest.

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?

Two tight sentences: purpose first, workflow guidance second. No repetition of schema or annotation content and nothing that could be cut without loss.

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

Completeness4/5

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

With no output schema, the description could have said more about what a suggestion record contains (keyword text plus popularity or bid data), but the workflow framing and annotation-covered safety profile make it callable as written. The unexplained "seed term" reference is the one real gap.

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 coverage is 100%, so the parameters (adamId, limit, savePath, adAccountId) are fully documented in structured data and the description need not repeat them. However, the phrase "or a seed term" implies an input that has no corresponding parameter, which mildly muddies rather than clarifies parameter semantics.

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?

"Ask Apple for keyword suggestions for an app" gives a specific verb (suggest) and resource (keywords) and is clearly distinguishable from sibling tools like apple_ads_list_keywords or apple_ads_get_search_term_popularity. The only blemish is the trailing "or a seed term", which names a capability the schema does not expose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly framed as "the research tool" with a sequencing rule (use before creating keywords) and a concrete companion call (apple_ads_get_report at level "search_term"). It stops short of stating when NOT to use it, e.g. vs. get_search_term_popularity, so it's strong but not fully exhaustive.

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