Skip to main content
Glama

Open data: clinical trials, EU tenders, companies, fuel prices

App Store App Search (iTunes API): prices, ratings, versions by country

app-store-search
Read-onlyIdempotent

Search Apple's App Store by keyword in any storefront country and get each app's developer, price, rating, version, release date, genre, size, minimum OS and store URL. Read from itunes.apple.com when called. Each result: app_id, name, developer, developer_id, bundle_id, price, formatted_price, currency, average_rating, rating_count, average_rating_current_version, rating_count_current_version, version, version_release_date, release_date, primary_genre, size_bytes, minimum_os, content_rating, seller_name, store_url. Needs a RapidAPI key for this API (https://rapidapi.com/IanGregory/api/clinical-trials-eu-tenders-open-data-api), sent as the X-RapidAPI-Key header; the listing has a free plan.

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": "app-store-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoKeyword to search for in the App Store (for example budget, photo editor, meditation). Example: "budget".
limitNoHow many apps to return (Apple allows up to 200 per search). Example: 50.
countryNoTwo-letter App Store country code, which sets the prices, currency and ratings returned. Example: "us".

Output Schema

NameRequiredDescriptionDefault
countYeshow many results came back
itemsYesthe results, one object each
partialNosome of the source's requests failed: the results are incomplete
productNo
sourcesNowhere the data came from: each source's name, licence and the attribution to show with it
fetched_atNowhen the source was read (Unix seconds)
truncated_fromNothe answer was cut to fit: this many results came back in all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / sources
      Added value: +{
      +  "description": "where the data came from: each source's name, licence and the attribution to show with it",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "how many results came back",
      +      "type": "integer"
      +    },
      +    "fetched_at": {
      +      "description": "when the source was read (Unix seconds)",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "the results, one object each",
      +      "items": {
      +        "properties": {
      +          "app_id": {
      +            "description": "app_id (id)"
      +          },
      +          "average_rating": {
      +            "description": "average_rating (number)"
      +          },
      +          "average_rating_current_version": {
      +            "description": "average_rating_current_version (number)"
      +          },
      +          "bundle_id": {
      +            "description": "bundle_id (text)"
      +          },
      +          "content_rating": {
      +            "description": "content_rating (text)"
      +          },
      +          "currency": {
      +            "description": "currency (currency)"
      +          },
      +          "developer": {
      +            "description": "developer (text)"
      +          },
      +          "developer_id": {
      +            "description": "developer_id (id)"
      +          },
      +          "formatted_price": {
      +            "description": "formatted_price (text)"
      +          },
      +          "minimum_os": {
      +            "description": "minimum_os (text)"
      +          },
      +          "name": {
      +            "description": "name (text)"
      +          },
      +          "price": {
      +            "description": "price (price)"
      +          },
      +          "primary_genre": {
      +            "description": "primary_genre (text)"
      +          },
      +          "rating_count": {
      +            "description": "rating_count (integer)"
      +          },
      +          "rating_count_current_version": {
      +            "description": "rating_count_current_version (integer)"
      +          },
      +          "release_date": {
      +            "description": "release_date (datetime)"
      +          },
      +          "seller_name": {
      +            "description": "seller_name (text)"
      +          },
      +          "size_bytes": {
      +            "description": "size_bytes (integer)"
      +          },
      +          "store_url": {
      +            "description": "store_url (url)"
      +          },
      +          "version": {
      +            "description": "version (text)"
      +          },
      +          "version_release_date": {
      +            "description": "version_release_date (datetime)"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "partial": {
      +      "description": "some of the source's requests failed: the results are incomplete",
      +      "type": "boolean"
      +    },
      +    "product": {
      +      "type": "string"
      +    },
      +    "truncated_from": {
      +      "description": "the answer was cut to fit: this many results came back in all",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.8/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, openWorld, non-destructive), yet the description adds real context beyond them: a live network read from itunes.apple.com, an API-key requirement sent as the X-RapidAPI-Key header, and the existence of a free plan. The credibility of that auth guidance is undercut because the linked RapidAPI listing is for 'clinical-trials-eu-tenders-open-data-api', a clearly mismatched URL that could send an agent to the wrong subscription.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the auth note is well placed, but the 21-field enumeration duplicates the output schema verbatim and consumes most of the text, and the whole body is delivered as run-on sentences. Roughly a third of the content earns its place twice over.

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 three-parameter, zero-required read tool with a full output schema, this covers purpose, network behavior, auth, and result shape with nothing critical missing. The only completeness defect is the wrong RapidAPI listing URL, which is the one piece of operational information an agent would actually need.

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% and both the 200-result cap and the country-code-to-currency relationship are already documented in the schema. The description restates the country effect ('sets the prices, currency and ratings') but adds no new parameter meaning, so the baseline of 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 and resource ('Search Apple's App Store by keyword') plus scope ('in any storefront country') and enumerates the dimensions returned (price, rating, version, genre). Sibling tools are all in unrelated domains, so no differentiation burden exists and an agent can select this tool from the name plus first clause 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: an agent can infer this is the tool for keyword-based App Store lookups, and the description notes that country governs prices/currency/ratings. However, it never says when not to use it, whether results are ranked or exhaustive, or how to page beyond the limit, so guidance remains implicit.

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