SiteCheck Agent Intel & Dev

Mac App Store app metadata from Apple's public iTunes

dev_mac_app_store

Read-only

Mac App Store app metadata from Apple's public iTunes Lookup API by App Store id: name, seller, version, price, average rating and rating count (0 when Apple shows none), genre and store link. Mac apps only. Related tools on this server, for a different need: dev_apple_app_store_iphone when you need App Store iPhone app metadata from Apple's public iTunes; dev_apple_app_store_reviews when you need App Store customer reviews of one iOS app from Apple's. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "id": "<id>"
    },
    "name": "dev_mac_app_store"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Mac App Store track id, digits only, e.g. 497799835 (Xcode)
`country`	No	Two-letter store country code (default us)

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`genre`	No
`price`	No
`seller`	No
`source`	No
`country`	No
`version`	No
`currency`	No
`storeUrl`	No
`checkedAt`	No
`ratingCount`	No
`releaseDate`	No
`averageRating`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds meaningful behavior: rating count is reported as 0 when Apple shows none, results are limited to Mac apps, and billing is $0.002 USDC per successful call with failed calls not charged. That failure/charge semantics is exactly the kind of context annotations cannot express. It stops short of describing rate limits or caching/refresh behavior.

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 content is front-loaded: resource, source, keyed identifier and returned fields come first, followed by exclusions, alternatives and pricing. It is dense but every clause carries information. The pricing sentence is slightly long with parenthetical provider enumeration, a minor cost.

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

Completeness5/5

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

For a two-parameter read-only lookup with an output schema already covering return values and annotations covering the safety profile, the description supplies everything an agent needs: what it returns, the Mac-only constraint, the alternative tools, and the payment model for a paid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already carry descriptions plus a concrete example id, so the baseline is 3. The description reinforces the meaning of 'id' as an App Store track id and ties it to the returned record, but it adds no new detail about the country parameter beyond what the schema already documents.

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 states a specific verb-and-resource pair (fetch Mac App Store app metadata via Apple's public iTunes Lookup API, keyed by App Store id) and enumerates the returned fields (name, seller, version, price, rating, genre, link). It also draws a hard boundary with 'Mac apps only' and names the sibling that serves the iPhone case, so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

It gives explicit routing: use dev_apple_app_store_iphone for iPhone app metadata and dev_apple_app_store_reviews for customer reviews of one iOS app. It also states the exclusion ('Mac apps only'), which tells the agent when this tool is the wrong choice, not just when it is the right one.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?