Skip to main content
Glama
paulet4a-commits

WebDataTools Developer, app & research data MCP server

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

app_store_lookup

Look up iOS app details—ratings, price, version, size, genres, and charts—by App Store ID, bundle ID, URL, or search term. Fetch Top Free or Top Paid rankings by country.

Instructions

App Store lookup for iOS apps: ratings, price, version, update date, size, genres and description from any app id, bundle id, store URL or search term — plus Top Free and Top Paid charts. Billed to your own Apify account: ~$0.001 per result (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appsYesApps to look up — Enter one app per row in any of four forms: a numeric App Store id (324684580), a bundle id (com.spotify.client), an App Store URL (https://apps.apple.com/us/app/spotify-music/id324684580), or a search term prefixed with search: (search:meditation, which returns up to searchLimit apps). Used in lookup mode only. Example: ["324684580"].
modeNoMode — Choose lookup to resolve the apps you list below, or topCharts to download a storefront's Top Free or Top Paid chart. In topCharts mode the apps field is ignored and chart, chartLimit and country decide the output. Options: lookup = Lookup apps I list; topCharts = Top charts for a country.lookup
chartNoChart — Pick which chart to download in topCharts mode. Apple's public RSS feed serves only these two for apps — there is no top-grossing feed (it returns HTTP 404). Options: top-free = Top Free Apps; top-paid = Top Paid Apps.top-free
countryNoStorefront country — Enter the two-letter country code of the App Store storefront to read, e.g. us, gb, de, jp. Prices, ratings, descriptions and chart positions are all storefront-specific, so us and de can return different numbers for the same app.us
chartLimitNoChart size — Enter how many ranked apps to return in topCharts mode, e.g. 50. Apple's feed only serves 10, 25, 50 or 100 positions; any other number (including this field's own min/max) is rounded up to the nearest one of those four.
searchLimitNoResults per search term — Enter how many apps each search: term should return, e.g. 25. Apple's Search API caps this at 200. Only affects rows starting with search: — an id or bundle id always returns exactly one row.
enrichChartAppsNoEnrich chart rows with full metadata — Keep this on so every charted app also gets its ratings, price, version, size and description from the iTunes lookup API. Apple's chart feed alone only carries name, developer, icon and release date. Turning it off makes a 100-app chart two requests cheaper but leaves those columns null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers an important non-obvious behavior: billing to the caller's own Apify account with a per-result price (~$0.001) that varies by plan. That is genuine cost/behavioral context an agent cannot get from the schema. It does not, however, describe auth requirements, rate limits, or failure behavior.

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?

A single dense sentence front-loads the resource and returned fields, then appends the pricing clause. No filler, no redundancy, and the most decision-relevant facts come first.

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?

For a 7-parameter, two-mode scraper with no output schema and no annotations, the description covers purpose, accepted input forms, chart support, and cost. It does not describe the shape of returned records or behavior when a lookup fails, which a mutation-free read tool of this size would ideally mention, keeping it from a 5.

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 defines every parameter with examples, ranges, and rounding rules. The description's mention of the four input forms and the two charts largely restates what the schema documents, so the baseline 3 applies.

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?

States a specific verb+resource ('App Store lookup for iOS apps') and enumerates the returned fields (ratings, price, version, update date, size, genres, description) plus lookup vs chart coverage. It is clearly distinguishable from the Android-oriented sibling google_play_scraper.

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?

The description frames the two operating modes ('from any app id, bundle id, store URL or search term — plus Top Free and Top Paid charts'), which tells an agent what inputs are acceptable. It stops short of explicit when-to-use/when-not guidance or naming an alternative tool for edge cases, so it lands below a 5.

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