Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Search the App Store and Google Play

search_app_stores
Read-onlyIdempotent

Search Apple App Store and Google Play by keywords, app links, or top charts and retrieve app metadata for market research, ASO, and competitor tracking.

Instructions

Apps from the Apple App Store and Google Play by search words, app links or top charts: name, developer, rating, rating count, price, category, release and update dates, size, version, description and store link. Useful for app market research, ASO and competitor tracking. Runs the Apify Actor tacps126/app-stores on your Apify account (about $0.0006 per app; spend per call is capped at $0.5).

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

Input Schema

NameRequiredDescriptionDefault
appsNoApp Store or Google Play links, or Play package names, e.g. ["com.spotify.music"].
chartsNoApp Store top charts in the country, with position.
storesNoStores for search words (default both).
countryNoTwo-letter store country, e.g. "us", "gb", "in".us
queriesNoSearch words, e.g. ["budget tracker"].
free_onlyNoOnly free apps.
max_itemsNoMaximum results to return (default 100, max 2000). Cost scales with this.
min_ratingNoOnly apps rated at least this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare that this is read-only, open-world, idempotent, and non-destructive, so the description does not need to restate that. It adds valuable operational context by naming the underlying Apify Actor, noting that it runs on the user's Apify account, and disclosing per-app cost plus a $0.5 per-call spend cap.

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 description is compact and front-loads the core search capability, then adds returned fields, use cases, and cost information. The first sentence is dense and noun-first rather than verb-first, but overall it is efficient and has no obvious filler.

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?

Given the annotations, full schema descriptions, and the presence of an output schema, the definition supplies what an agent needs: what it searches, which stores, what fields it returns, primary use cases, and cost/account implications. No critical behavioral or contextual information appears missing.

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 the schema already documents all nine parameters, including defaults, limits, and examples. The description reinforces the three input modes—search words, app links, and top charts—but adds little parameter-level meaning beyond the schema.

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: searching apps across the Apple App Store and Google Play via search words, app links, or top charts, and it lists the returned app fields. It is clear, but it does not explicitly distinguish itself from the close sibling get_app_reviews.

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 clear use contexts such as app market research, ASO, and competitor tracking, which helps an agent decide when the tool is relevant. It does not state exclusions or explicitly compare itself with alternatives such as review-focused tools.

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