Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browse_sitemap

Browse an Apple Store sitemap by country to retrieve links, with an optional keyword filter for finding product pages when search is unavailable.

Instructions

Browse the Apple Store sitemap for a country and return links, optionally filtered by a keyword. Useful for discovering product pages when search is unavailable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass the process cache and request current shop data.
queryNoOptional filter for link text or URL.
countryNoStorefront country code, e.g. us, de, fr, ch, be. Use list_storefronts for supported values.us
languageNoShop language; defaults to the country's main language. Switzerland: de/fr; Belgium: fr/nl; Canada: en/fr.

Output Schema

NameRequiredDescriptionDefault
cacheNo
countYes
linksYes
queryNo
countryNous
languageNoen
retailerYes
observed_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 bears the full disclosure burden. It does say it browses a sitemap and returns links, which is genuine behavioral context, but it omits anything about sitemap size, result volume, pagination, or rate limits; the caching behavior is only covered indirectly via the schema's 'fresh' parameter.

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?

Two tight sentences with the action and return value front-loaded, followed by the fallback use case. Nothing is redundant, though the second sentence could have named the fallback tool more concretely.

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-value explanation is unnecessary, and all four parameters are documented in the schema with sensible defaults. The gaps are minor: no note on result volume or whether the sitemap is comprehensive, which would matter for a browsing tool.

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 every parameter already carries a description, including country codes, language defaults per country, and the cache-bypass flag. The description only restates the keyword filter and country scoping that the schema already defines, adding no new syntax or format detail.

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 states a specific verb and resource ('Browse the Apple Store sitemap for a country') and names the payload ('return links'), so an agent knows exactly what comes back. It stops short of naming a specific sibling tool, but the phrase 'when search is unavailable' implicitly contrasts it with the search tools in the catalog.

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?

It gives a clear when-to-use condition: discovering product pages when search is unavailable. There are no explicit exclusions or named alternatives (e.g. search_products, explore_product), so the routing is implied rather than spelled out.

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

Deploy Server

Other Tools