play-store-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAY_STORE_MCP_LOG_LEVEL | No | Log level (DEBUG, INFO, WARNING, ERROR). Default: INFO. | INFO |
| GOOGLE_PLAY_STORE_CREDENTIALS | No | Inline JSON credentials string (alternative to GOOGLE_APPLICATION_CREDENTIALS). | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to service account JSON key file. Required unless using per-request credentials. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search for available tools by query. Returns matching tools ranked by relevance. |
| get_schemaA | Get parameter schemas for specific tools. Use after searching to get the detail needed to call a tool. |
| executeA | Chain |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool occupies a clearly separate stage of the workflow: search discovers tools, get_schema inspects parameters, and execute runs the actual call. There is no overlap or ambiguity between them.
Tool names are all lowercase and verb-focused, with get_schema following verb_noun while search and execute are bare verbs. The pattern is mostly predictable but not perfectly uniform.
Three tools is minimal but exactly matches the intended meta-workflow of discover, inspect, and execute. Each tool clearly earns its place, though the set is on the smaller end.
The workflow covers the full lifecycle from discovery to execution, enabling an agent to find and call tools effectively. A dedicated list-all-tools capability is missing, but search compensates for that gap.