Skip to main content
Glama

list_apps

Lists all accessible Google Play apps with package names, display names, and resource names. Use it to discover package names for use with other tools.

Instructions

List the apps this service account can access, each with packageName, displayName and a resource name. Use it to discover package names when GOOGLE_PLAY_PACKAGE_NAME is not set or when working across several apps — pass a packageName as the package_name argument of any other tool. Note displayName is the latest title set in the Play Console, which may not match the Play Store yet. Returns 50 apps by default, 1000 at most; pass page_token from nextPageToken to continue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax apps (default: 50)
page_tokenNonextPageToken from a previous call
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Discloses pagination behavior and a nuance about displayName, with no annotations to contradict.

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?

Concise and well-structured, front-loaded with purpose, then usage, notes, and pagination.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Sufficient given lack of output schema; covers purpose, usage, notes, and pagination for a complete understanding.

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?

Adds some context about pagination and default/max, but schema already describes parameters clearly.

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?

Clearly states it lists apps accessible by the service account, with specific attributes, using a verb and resource.

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?

Explicitly tells when to use it (discover package names) and contrasts with other tools by mentioning passing packageName to other tools.

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

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/OrellBuehler/play-console-mcp'

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