Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-permissions

Retrieve required permissions for Google Play apps to analyze security requirements and data access needs for market research and competitor analysis.

Instructions

Get permissions required by a Google Play app. Returns a list of permissions with:

  • permission: Description of the permission (e.g., 'modify storage contents')

  • type: Permission category (e.g., 'Storage', 'Network')

When short=true, returns just an array of permission strings. Note: Permissions are returned in the specified language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesGoogle Play package name (e.g., 'com.dxco.pandavszombies')
langNoLanguage code for permission text (default: en)en
countryNoCountry code to check app (default: us)us
shortNoReturn only permission names without categories (default: false)

Implementation Reference

  • The handler function that executes the tool logic by calling the gplay.permissions method from the google-play-scraper library and formatting the response as MCP content.
    async ({ appId, lang, country, short }) => {
      const permissions = await gplay.permissions({ appId, lang, country, short });
      return { content: [{ type: "text", text: JSON.stringify(permissions) }] };
    }
  • Zod schema defining the input parameters for the google-play-permissions tool.
      appId: z.string().describe("Google Play package name (e.g., 'com.dxco.pandavszombies')"),
      lang: z.string().default("en").describe("Language code for permission text (default: en)"),
      country: z.string().default("us").describe("Country code to check app (default: us)"),
      short: z.boolean().default(false).describe("Return only permission names without categories (default: false)")
    }, 
  • src/server.js:602-618 (registration)
    The server.tool registration for the google-play-permissions tool, including description, schema, and inline handler function.
    server.tool("google-play-permissions", 
      "Get permissions required by a Google Play app. Returns a list of permissions with:\n" +
      "- permission: Description of the permission (e.g., 'modify storage contents')\n" +
      "- type: Permission category (e.g., 'Storage', 'Network')\n\n" +
      "When short=true, returns just an array of permission strings.\n" +
      "Note: Permissions are returned in the specified language.",
      {
        appId: z.string().describe("Google Play package name (e.g., 'com.dxco.pandavszombies')"),
        lang: z.string().default("en").describe("Language code for permission text (default: en)"),
        country: z.string().default("us").describe("Country code to check app (default: us)"),
        short: z.boolean().default(false).describe("Return only permission names without categories (default: false)")
      }, 
      async ({ appId, lang, country, short }) => {
        const permissions = await gplay.permissions({ appId, lang, country, short });
        return { content: [{ type: "text", text: JSON.stringify(permissions) }] };
      }
    );
Behavior3/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 does well by describing the return format (list of permissions with fields) and the effect of the 'short' parameter. However, it doesn't mention potential limitations like rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though 'Get' implies reading). The description adds useful context but leaves gaps in behavioral understanding.

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 perfectly structured and concise. It starts with the core purpose, immediately describes the return format with clear bullet points, then adds two important notes about the 'short' parameter and language support. Every sentence earns its place with no wasted words, and the information is front-loaded appropriately.

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 tool's moderate complexity (4 parameters, no output schema, no annotations), the description provides good contextual coverage. It explains the return format in detail, clarifies parameter effects, and states the language dependency. The main gap is the lack of output schema, but the description compensates well by documenting the return structure. For a read-oriented tool with good schema coverage, this is nearly complete.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by explaining the effect of the 'short' parameter ('returns just an array of permission strings') and clarifying that permissions are returned in the specified language, which complements the schema's parameter descriptions. This additional semantic context elevates the score to 4.

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?

The description clearly states the tool's purpose: 'Get permissions required by a Google Play app' with a specific verb ('Get') and resource ('permissions'). It distinguishes from siblings like 'google-play-details' or 'google-play-datasafety' by focusing specifically on permissions. However, it doesn't explicitly contrast with all sibling tools, keeping it at 4 rather than 5.

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. With many sibling tools available (like 'google-play-datasafety' or 'google-play-details'), there's no indication of when permissions information is needed versus other app metadata. The description only explains what the tool does, not when it should be selected.

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