Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-datasafety

Retrieve Google Play app data safety details including collected and shared data types, security practices, and privacy policy links for compliance and security analysis.

Instructions

Get data safety information for a Google Play app. Returns an object with:

  • dataShared: Array of shared data items, each containing:

    • data: Name of the data being shared (e.g., 'User IDs')

    • optional: Boolean indicating if sharing is optional

    • purpose: Comma-separated list of purposes (e.g., 'Analytics, Marketing')

    • type: Category of data (e.g., 'Personal info')

  • dataCollected: Array of collected data items with same structure as dataShared

  • securityPractices: Array of security practices, each containing:

    • practice: Name of the security practice

    • description: Detailed description of the practice

  • privacyPolicyUrl: URL to the app's privacy policy

Data types can include: Personal info, Financial info, Messages, Contacts, App activity, App info and performance, Device or other IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesGoogle Play package name (e.g., 'com.dxco.pandavszombies')
langNoLanguage code for data safety info (default: en)en

Implementation Reference

  • The handler function that executes the tool: calls gplay.datasafety with appId and lang, then returns the result as JSON string in MCP content format.
    async ({ appId, lang }) => {
      const datasafety = await gplay.datasafety({ appId, lang });
      return { content: [{ type: "text", text: JSON.stringify(datasafety) }] };
    }
  • Zod input schema defining parameters: appId (required string), lang (optional string, defaults to 'en').
    {
      appId: z.string().describe("Google Play package name (e.g., 'com.dxco.pandavszombies')"),
      lang: z.string().default("en").describe("Language code for data safety info (default: en)")
    }, 
  • src/server.js:620-642 (registration)
    Full server.tool registration: name 'google-play-datasafety', detailed description of output, input schema, and inline handler function.
    server.tool("google-play-datasafety", 
      "Get data safety information for a Google Play app. Returns an object with:\n" +
      "- dataShared: Array of shared data items, each containing:\n" +
      "  - data: Name of the data being shared (e.g., 'User IDs')\n" +
      "  - optional: Boolean indicating if sharing is optional\n" +
      "  - purpose: Comma-separated list of purposes (e.g., 'Analytics, Marketing')\n" +
      "  - type: Category of data (e.g., 'Personal info')\n" +
      "- dataCollected: Array of collected data items with same structure as dataShared\n" +
      "- securityPractices: Array of security practices, each containing:\n" +
      "  - practice: Name of the security practice\n" +
      "  - description: Detailed description of the practice\n" +
      "- privacyPolicyUrl: URL to the app's privacy policy\n\n" +
      "Data types can include: Personal info, Financial info, Messages, Contacts,\n" +
      "App activity, App info and performance, Device or other IDs",
      {
        appId: z.string().describe("Google Play package name (e.g., 'com.dxco.pandavszombies')"),
        lang: z.string().default("en").describe("Language code for data safety info (default: en)")
      }, 
      async ({ appId, lang }) => {
        const datasafety = await gplay.datasafety({ appId, lang });
        return { content: [{ type: "text", text: JSON.stringify(datasafety) }] };
      }
    );
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 describes the return structure but doesn't mention important behavioral aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. The description is purely structural without operational context.

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?

The description is appropriately sized and front-loaded with the core purpose, followed by a structured breakdown of the return object. While comprehensive, every sentence serves a purpose in explaining the output format, making it efficient despite its length.

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?

For a read operation with 2 parameters and no output schema, the description adequately explains what information is returned. However, without annotations and with no output schema, it lacks important contextual details like error handling, data freshness, or limitations that would help an agent use it effectively.

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%, so the schema already fully documents both parameters. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 where the schema does the heavy lifting for parameter documentation.

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 states the specific action ('Get data safety information') and resource ('for a Google Play app'), distinguishing it from sibling tools like 'google-play-details' or 'google-play-permissions' by focusing exclusively on data safety information rather than general details or permissions.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'app-store-privacy' or explain the difference between data safety and privacy policy information, leaving the agent to infer usage context independently.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JiantaoFu/AppInsightMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server