Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_permissions

Retrieve the permissions a Google Play app requests by app ID. Optionally return only permission names or filter by country and language.

Instructions

Retrieve Google Play app permissions. Returns the permissions a Google Play app requests, by the required app_id. Each entry has the permission name and its type. Set short to get only the permission names as a flat list. country and lang pick the storefront and language.

Input Schema

NameRequiredDescriptionDefault
langNoTwo-letter language code
shortNoReturn only permission names
app_idYesGoogle Play app id
countryNoTwo-letter country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden and it does disclose the return shape: each entry has a permission name and type, and short returns a flat name list. It does not state read-only safety, auth needs, or rate limits, but the output disclosure is meaningful.

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?

Front-loaded with the purpose, then output shape, then the short toggle, then locale params. Four tight clauses with no filler and every sentence carrying distinct information.

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?

With no output schema or annotations, the description covers the return value (name + type, or flat list under short) and all four parameters, which is enough for a read tool. Missing auth/permission requirements keep it short of a 5.

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% (baseline 3), and the description goes further by explaining short's effect ('only the permission names as a flat list') and that country/lang pick storefront and language, adding effect-level meaning beyond the terse schema strings.

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?

States a specific verb (Retrieve) and resource (Google Play app permissions) keyed on the required app_id. The resource is distinct from Google Play siblings like googleplay_datasafety, googleplay_reviews, and googleplay_app, so an agent can route without opening schemas.

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?

Usage is implied by 'by the required app_id' and the description explains the short toggle, but it never states when to pick this tool over googleplay_app or googleplay_datasafety, nor any prerequisites or exclusions.

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