Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_datasafety

Retrieve Google Play data safety details for an app by app ID, including data collected and shared, purposes, optional status, security practices, and privacy policy URL.

Instructions

Retrieve Google Play data safety details. Returns the data safety section Google Play shows for an app, by the required app_id. It lists the data the app collects and shares, each with its type, purpose and whether it is optional, plus the app's security practices and privacy policy URL. lang sets the language.

Input Schema

NameRequiredDescriptionDefault
langNoTwo-letter language code
app_idYesGoogle Play app id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return contents in detail (collected/shared data with type, purpose, optional flag, security practices, privacy policy URL) and the verb 'Retrieve' signals a non-destructive read. It stops short of noting auth or rate-limit behavior, but the behavioral profile is otherwise clear.

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?

Front-loaded with purpose, then return contents, then the lang note. Three sentences with no filler. The middle sentence is dense but informative rather than wasteful, so it stays efficient overall.

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 two-parameter read tool with no output schema, the description adequately covers what is returned and what each parameter does, so an agent can call it correctly. Only the absence of usage routing and any auth notes keeps it from being fully complete.

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 100%, so the schema already documents both parameters. The description only restates that app_id is required and that lang sets the language, adding little syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource ('Retrieve Google Play data safety details') and immediately scopes it to the data safety section of an app, which is clearly distinct from siblings like googleplay_permissions or googleplay_ratings. It does not explicitly name a sibling to route against, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative is given. The agent can infer this is the tool for data safety info, but nothing tells it to prefer this over googleplay_app or googleplay_permissions, nor when lang should be set.

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