Crypto, web, finance and app data tools

app_store_search

Search the Apple App Store for a keyword and get up to 50 apps in rank order with full details. Use for ASO keyword research or finding competing apps.

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": {
      "q": "<q>"
    },
    "name": "app_store_search"
  }
}

Input Schema

Name	Required	Default
`q`	Yes
`limit`	No
`country`	No	us

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

removedInput schema / properties / store

Removed value: -{
-  "default": "google",
-  "title": "Store",
-  "type": "string"
-}

AddedOct 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses the hard cap of 50 results and that results come back in rank order with full details, but says nothing about rate limits, whether an API key is needed, or whether the 50 is a pagination ceiling or a total.

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?

Two tight sentences, front-loaded with the action and result shape, followed by the use case. No filler or restated name.

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

Completeness3/5

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

Output schema exists so return values needn't be explained, and the 50-result cap is covered. But the country parameter's purpose (storefront selection) and default are unaddressed, and no auth or rate-limit context is given.

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 coverage is 0%, so the description must compensate. It adds real meaning for q (keyword) and limit (max 50, not stated in schema which has no maximum), but the country parameter is never mentioned, leaving one of three parameters completely undocumented.

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?

Specific verb (search) plus resource (Apple App Store) plus output shape (up to 50 apps in rank order with full details). It implicitly distinguishes itself from siblings like app_store_details and app_store_reviews by being keyword-driven, but never names them.

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?

Gives concrete usage context: ASO keyword research and finding competing apps. No explicit exclusions or routing to app_store_details (single-app lookup) or app_store_reviews, so the agent must infer the boundary itself.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?