Skip to main content
Glama
Sign In
appstore-play-mcp

appstore-play-mcp

by JohnBilousov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get one app

get_app
Read-only

Retrieve detailed app information using its App Store ID, Play package name, or bundle ID. Get store-specific or merged details from both stores.

Instructions

Details for a single app, found by App Store id, Play package name, or bundle id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "get_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp Store numeric id, Play package name, or bundle id
storeNoWhich store to read. Defaults to every store that is configured

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, signaling a safe read operation. The description adds the identifier context but not deeper behavioral traits like error handling or response format, which is reasonable given the annotations. No contradiction with annotations.

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?

A single, to-the-point sentence that front-loads the resource ('single app') and the accepted identifiers. No wasted words; the description is efficient and immediately informative.

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 simple lookup with two parameters (one optional) and no output schema, the description adequately informs the agent. It specifies the identifier types and the tool's purpose, though it omits explicit differentiation from siblings—a minor gap given the tool's simplicity.

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 schema covers both parameters fully (appId description and store enum with description). The description's mention of identifier formats mirrors the schema exactly, adding no new semantic value beyond the structured data. Baseline 3 applies given 100% schema coverage.

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 states a specific action (retrieve details) on a clear resource (a single app) and lists the accepted identifier formats (App Store id, Play package name, or bundle id). This distinguishes it from sibling tools like list_apps (lists multiple apps) and get_releases/reviews (focus on specific aspects).

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 does not explicitly state when to use this tool versus alternatives like list_apps or get_releases. It only says what it does, leaving the agent to infer that for a single app's details this is the appropriate choice. No exclusion conditions or 'see also' guidance are provided.

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

Deploy Server

Other Tools