Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-categories

Retrieve Google Play Store category identifiers for filtering apps in market research and competitor analysis.

Instructions

Get list of all Google Play categories. Returns an array of category identifiers like:

  • 'APPLICATION': All applications

  • 'GAME': All games

  • 'ANDROID_WEAR': Wear OS apps

  • 'SOCIAL': Social apps

  • 'PRODUCTIVITY': Productivity apps etc.

These category IDs can be used with the google-play-list tool to filter apps by category. Sample response: ['AUTO_AND_VEHICLES', 'LIBRARIES_AND_DEMO', 'LIFESTYLE', ...]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function executes the tool logic by calling gplay.categories() to retrieve all Google Play category identifiers and returns the result as a JSON string in MCP content format.
    async () => {
      const categories = await gplay.categories();
      return { content: [{ type: "text", text: JSON.stringify(categories) }] };
    }
  • The input schema is empty, indicating the tool requires no parameters.
    {}, // No parameters needed
  • src/server.js:644-659 (registration)
    The registration of the 'google-play-categories' tool using McpServer.tool(), including description, schema, and inline handler function.
    server.tool("google-play-categories", 
      "Get list of all Google Play categories. Returns an array of category identifiers like:\n" +
      "- 'APPLICATION': All applications\n" +
      "- 'GAME': All games\n" +
      "- 'ANDROID_WEAR': Wear OS apps\n" +
      "- 'SOCIAL': Social apps\n" +
      "- 'PRODUCTIVITY': Productivity apps\n" +
      "etc.\n\n" +
      "These category IDs can be used with the google-play-list tool to filter apps by category.\n" +
      "Sample response: ['AUTO_AND_VEHICLES', 'LIBRARIES_AND_DEMO', 'LIFESTYLE', ...]",
      {}, // No parameters needed
      async () => {
        const categories = await gplay.categories();
        return { content: [{ type: "text", text: JSON.stringify(categories) }] };
      }
    );
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 clearly describes what the tool returns ('Returns an array of category identifiers'), provides examples of the output format, and mentions a sample response. However, it doesn't address potential limitations like rate limits or authentication requirements.

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 efficiently structured with a clear purpose statement, examples, and usage guidance in three concise paragraphs. Every sentence adds value, though the bulleted list of examples could be slightly condensed.

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 zero-parameter tool with no output schema, the description provides good context: it explains what the tool does, shows example outputs, and connects it to related tools. However, without annotations or output schema, it could benefit from more explicit behavioral details like response format guarantees.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the output and usage context.

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 list of all Google Play categories') and resource ('Google Play categories'), distinguishing it from sibling tools like google-play-list which filters apps by category. It explicitly names the tool's purpose without being tautological.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('These category IDs can be used with the google-play-list tool to filter apps by category'), providing clear guidance on its purpose in relation to an alternative tool. It effectively distinguishes this from other sibling tools that perform different operations.

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