Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_developer

List Google Play apps published by a developer using their ID or name, with optional country, language, result count, and full-detail lookup.

Instructions

Retrieve apps by Google Play developer. Lists the Google Play apps published by one developer, by developer id or name, for an optional country and language. num sets how many apps to return, and full_detail=true resolves each app to its full detail record instead of the listing summary. Returns the developer id and name with the app list.

Input Schema

NameRequiredDescriptionDefault
numNoNumber of apps
langNoTwo-letter language code
dev_idYesDeveloper id or name
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 the full behavioral burden. It usefully discloses the full_detail toggle semantics (full detail record vs listing summary) and what the response contains ('developer id and name with the app list'), but says nothing about auth, rate limits, pagination, or error behavior.

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?

Purpose is front-loaded in the first sentence with parameters and return value following. Three sentences with minimal waste, though the num/full_detail clause is a little densely packed.

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 5-parameter list tool with no annotations and no output schema, the description covers purpose, key parameter behavior, and the return payload well. It lacks detail on the summary-vs-detail field composition, but otherwise is callable as-is.

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 3 is the floor, but the description adds real meaning: it clarifies that dev_id accepts an id or a name and that full_detail resolves to the full record 'instead of the listing summary', which the terse schema text does not.

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?

States a specific verb ('Retrieve apps') and scoping resource ('by Google Play developer'), naming the developer id/name, country, and language dimensions. An agent can distinguish it from googleplay_search or googleplay_list by the developer-centric scope, though no sibling is named explicitly.

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 (pulling all apps from a known developer) but never states when to prefer this over googleplay_search or googleplay_list, nor any exclusions or prerequisites. It is only implied guidance.

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