Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_similar

Find similar Google Play apps by providing an app ID. Returns apps from the 'Similar apps' cluster to help you discover related apps.

Instructions

Retrieve similar Google Play apps. Returns apps from the "Similar apps" cluster on an app details page.

Input Schema

TableJSON 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.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that it retrieves similar apps from a specific cluster, but fails to mention any behavioral traits such as read-only nature, authentication requirements, rate limits, or error handling for invalid app_ids. This lack of detail is a significant gap.

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?

The description is extremely concise—two sentences with zero waste. It front-loads the action and resource, making it easy for an agent to quickly grasp the tool's purpose.

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?

The description misses details about what the returned data looks like (no output schema) and how the 'Similar apps' cluster is defined. Given the moderate complexity (5 params, many sibling tools), the description is adequate but leaves gaps in understanding for an AI agent.

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% (all 5 parameters are described in the schema). The tool description adds no additional parameter information beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

The description clearly specifies the verb 'Retrieve' and the resource 'similar Google Play apps', and pinpoints the source as the 'Similar apps' cluster on an app details page. This distinguishes it from sibling tools like googleplay_app (single app details) or googleplay_search (search).

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?

The description implies usage when you have an app id and want similar apps, but does not explicitly state when to use this tool versus alternatives like googleplay_search or appstore_similar. No exclusions or alternative recommendations are provided.

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