Fetch Google Play data safety details for any app ID to see what data the app collects, shares, and how it protects user information.
Retrieve Google Play data safety details. Returns the data safety information displayed on Google Play.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Two-letter language code | |
| app_id | Yes | Google Play app id |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It only states the function without disclosing read-only nature, rate limits, error handling, or behavior when data safety info is absent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but contains redundancy between 'Retrieve...' and 'Returns...' Could be more concise. Adequate but not exemplary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema or explanation of return values. Does not describe potential errors or response format. Incomplete for a tool with no annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters with clear descriptions. The description adds no additional parameter info beyond schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves Google Play data safety details, using a specific verb and resource. It distinguishes from sibling tools like googleplay_permissions or googleplay_reviews.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like googleplay_app or googleplay_permissions. No mention of prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.