Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-privacy

Retrieve detailed privacy information for App Store apps, including data collection categories, usage purposes, and management options for user privacy choices.

Instructions

Get privacy details for an App Store app. Returns an object with:

  • managePrivacyChoicesUrl: URL to manage privacy choices (if available)

  • privacyTypes: Array of privacy data types, each containing:

    • privacyType: Name of the privacy category

    • identifier: Unique identifier for the privacy type

    • description: Detailed description of how data is used

    • dataCategories: Array of data categories, each containing:

      • dataCategory: Category name

      • identifier: Category identifier

      • dataTypes: Array of specific data types collected

    • purposes: Array of purposes for data collection Note: Currently only available for US App Store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric App ID (e.g., 553834731)

Implementation Reference

  • The handler function for the 'app-store-privacy' tool. It takes an app ID, fetches privacy details using the external 'store.privacy' method from '@jeromyfu/app-store-scraper', and returns the result as a JSON string in the MCP content format.
    async ({ id }) => {
      const privacy = await store.privacy({ id });
      return { content: [{ type: "text", text: JSON.stringify(privacy) }] };
    }
  • Zod schema for input validation: requires a numeric 'id' parameter representing the App Store app ID.
      id: z.number().describe("Numeric App ID (e.g., 553834731)")
    },
  • src/server.js:249-269 (registration)
    Registration of the 'app-store-privacy' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool("app-store-privacy", 
      "Get privacy details for an App Store app. Returns an object with:\n" +
      "- managePrivacyChoicesUrl: URL to manage privacy choices (if available)\n" +
      "- privacyTypes: Array of privacy data types, each containing:\n" +
      "  - privacyType: Name of the privacy category\n" +
      "  - identifier: Unique identifier for the privacy type\n" +
      "  - description: Detailed description of how data is used\n" +
      "  - dataCategories: Array of data categories, each containing:\n" +
      "    - dataCategory: Category name\n" +
      "    - identifier: Category identifier\n" +
      "    - dataTypes: Array of specific data types collected\n" +
      "  - purposes: Array of purposes for data collection\n" +
      "Note: Currently only available for US App Store.",
      {
        id: z.number().describe("Numeric App ID (e.g., 553834731)")
      },
      async ({ id }) => {
        const privacy = await store.privacy({ id });
        return { content: [{ type: "text", text: JSON.stringify(privacy) }] };
      }
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the return structure in detail (object with managePrivacyChoicesUrl, privacyTypes array, etc.) and notes the geographic limitation ('only available for US App Store'), which are crucial behavioral traits. It does not mention error handling, rate limits, or authentication needs, but provides substantial context beyond the basic purpose.

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?

The description is appropriately sized and front-loaded: it starts with the core purpose, immediately details the return structure in a clear bulleted list, and ends with a critical note on availability. Every sentence earns its place by providing essential information without redundancy or fluff.

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?

Given the complexity of returning structured privacy data, no annotations, and no output schema, the description does a strong job by detailing the return object structure extensively. It covers the key components (managePrivacyChoicesUrl, privacyTypes with nested arrays) and adds the geographic limitation. However, it lacks information on error cases or response formats for missing data, which slightly reduces completeness for a tool with no structured output schema.

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?

The input schema has 100% description coverage, with the 'id' parameter clearly documented as 'Numeric App ID (e.g., 553834731).' The description adds no additional parameter information, as it focuses on the output structure. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without param details in the description, which applies here.

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 privacy details') and resource ('for an App Store app'), distinguishing it from sibling tools like app-store-details, app-store-ratings, or google-play-datasafety. It precisely defines the scope as privacy information rather than general details, ratings, or other app metadata.

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 context by specifying 'Currently only available for US App Store,' which provides a geographic limitation. However, it lacks explicit guidance on when to use this tool versus alternatives like google-play-datasafety for Android apps or other App Store tools for non-privacy data, and does not mention prerequisites or exclusions beyond the geographic note.

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