Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

googleplay_similar

Retrieve apps in the Similar apps cluster for a Google Play app ID; set count, country, language, or request full details.

Instructions

Retrieve similar Google Play apps. Returns the apps in the Similar apps cluster on a Google Play app page, for the required app_id. num limits how many are returned, country and lang set the storefront and language, and full_detail returns full app details instead of compact cards.

Input Schema

NameRequiredDescriptionDefault
numNoNumber of apps
langNoTwo-letter language code
app_idYesGoogle Play app id
countryNoTwo-letter country code
full_detailNoResolve each app to full detail

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It usefully discloses the return shape (compact cards vs. full app details via `full_detail`) and that results come from a curated cluster. It still omits rate-limit, error, and pagination behavior, but 'Retrieve' clearly signals a read-only lookup.

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?

Three tight sentences, front-loaded with the purpose, then return shape, then a compact parameter map. No filler, though the parameter enumeration reads slightly list-like.

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 simple seeded lookup with no output schema and no annotations, the description covers purpose, return shape, and all five parameters. Nothing critical to correct invocation is missing, though pagination/limit interplay for `num` is unstated.

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?

Schema coverage is 100%, so baseline is 3. The description adds real value beyond the terse schema: `num` limits return count, `country`/`lang` set storefront and language (framing them as storefront controls), and `full_detail` switches between compact cards and full details — semantics not conveyed by 'Resolve each app to full detail'.

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+resource: 'Retrieve similar Google Play apps' and it clarifies these come from the 'Similar apps cluster on a Google Play app page'. This distinguishes it from search/list tools. However, it doesn't explicitly name or route against any sibling (e.g., appstore_similar or googleplay_app), so it's clear but not maximally differentiating.

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?

It notes the operation is keyed on a required `app_id`, which implies you need an existing app to seed the lookup. But it gives no explicit when-to-use/when-not guidance and names no alternative tool (such as googpleay_search) for finding apps when you don't already have an app_id.

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