Skip to main content
Glama

FoxAPIs data sources

App Store app

appstore_app
Read-onlyIdempotent

An App Store listing: rating, number of ratings, price, category, version, size and last update, from its link. Costs 8 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": "appstore_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://apps.apple.com/us/app/instagram/id389801252"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description correctly spends its space on non-obvious operational facts: 8 credits per call, no charge when no data is returned, and an API-key prerequisite. Those are exactly the cost and auth details annotations cannot express. It omits what an empty or failed response looks like beyond the billing note.

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?

Three short sentences with the payoff (what you get) front-loaded, followed by cost and auth. No filler, no repetition of the title, and every clause carries information the agent cannot get from the structured fields.

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 shoulders the burden of describing return values, and it does so by enumerating the seven fields. Cost, billing exception, and key requirement round out the operational picture. Only the failure/empty-result behavior and the response shape remain underspecified.

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?

Only one parameter, and the schema documents it at 100% coverage with a concrete example URL, so the baseline is already high. The description's 'from its link' reinforces that the url must point at a specific listing rather than a search or developer page, which is a small but real addition.

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 names the resource precisely (an App Store listing) and enumerates the fields returned: rating, rating count, price, category, version, size, last update. It also establishes the input shape ('from its link'). It stops short of explicitly contrasting with the sibling googleplay_app, so an agent must infer the platform distinction from the name alone.

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?

Usage is implied rather than stated: pass an App Store URL, receive listing metadata. There is no explicit when-to-use condition, no exclusion, and no named alternative, though the credit cost does implicitly signal this is a metered call to reserve for real lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources