Apple Store MCP

Overview Schema Source Related Servers Discussions Admin

explore_product

Browse Apple product choices, variants, and prices; add a location for nearby store quotes or a postal code for delivery estimates. Read-only—no reservations or purchases.

Instructions

Explore product choices, variants and prices; add a location for nearby store quotes or postal_code for delivery estimates. Read-only; no reservation or purchase.

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": {
      "url": "<url>"
    },
    "name": "explore_product"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Apple product page or buy link returned by search or a previous call.
`country`	No	Storefront country code, e.g. us, de, fr, ch, be. Use list_storefronts for supported values.	us
`options`	No	Optional choices, e.g. {"memory": "48 GB"}. To preserve a previous configuration, pass its selection object with the desired changes.
`language`	No	Shop language; defaults to the country's main language. Switzerland: de/fr; Belgium: fr/nl; Canada: en/fr.
`location`	No	Optional city or postal code to check nearby store availability.
`postal_code`	No	Optional delivery postal code.

Output Schema

Name	Required	Description	Default
`url`	Yes
`kind`	Yes
`price`	No
`issues`	No
`stores`	No
`choices`	No
`options`	No
`currency`	No
`delivery`	No
`location`	No
`variants`	No
`selection`	No
`observed_at`	No
`price_display`	No
`availability_observed_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose the key behavioral trait 'Read-only; no reservation or purchase,' which reassures the agent no mutation occurs. It stops short of covering auth needs, rate limits, or whether quotes/estimates are live versus cached.

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 tightly written sentences with the core capability front-loaded and the read-only caveat tacked on last. There is no filler or redundancy.

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?

An output schema exists, so return values needn't be explained, and all six parameters are documented. The read-only nature is stated, which compensates for the missing annotations. Only the sibling-selection guidance is thin given how many overlapping availability tools exist.

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%, so the schema already documents every parameter including url, country, options, language, location, and postal_code. The description echoes the purpose of location and postal_code but adds little syntax or format detail beyond the schema, so baseline 3 applies.

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 gives a specific verb and scope: 'Explore product choices, variants and prices,' plus the location/postal_code add-ons for store quotes and delivery estimates. It is clear what the tool does, but it does not distinguish itself from siblings like get_product or search_products, so an agent must infer the boundary.

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?

It explains the two optional capabilities (location for nearby store quotes, postal_code for delivery estimates) which implies a usage context. However, it offers no explicit 'use this instead of X' guidance against the many availability/delivery siblings, leaving selection to inference.

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

Deploy Server