Skip to main content
Glama

App details

get_app_details
Read-only

App listing summaries for up to 50 IDs; unavailable apps are omitted. Descriptions and screenshot URLs are excluded unless includeDescription/includeScreenshots is true. No icon URLs. Counts toward the research quota.

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": {
      "appStoreIds": "<appStoreIds>"
    },
    "name": "get_app_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNous
appStoreIdsYes
includeDescriptionNo
includeScreenshotsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / includeDescription
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / includeScreenshots
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses several non-obvious behaviors: unavailable IDs are silently dropped, description text and screenshot URLs are suppressed by default, icon URLs are never returned, and the call consumes research quota. Those omissions and the quota cost are exactly the kind of context the annotations cannot express.

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?

Four short clauses with no filler, and the most important facts (batch summaries, omitted apps) come first. The telegraphic, semicolon-joined phrasing is dense but occasionally reads as notes rather than prose.

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

Completeness3/5

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

There is no output schema, so the description must carry the return-value burden; it names the shape only loosely ('summaries') and lists what is excluded, but never says which fields are included. Combined with the unexplained 'store' parameter, an agent still has gaps for a 4-parameter, quota-consuming call.

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?

With 0% schema description coverage, the description compensates partially: it clarifies the semantics of includeDescription/includeScreenshots (excluded unless set true) and the 50-ID ceiling on appStoreIds. It says nothing about the 'store' parameter (default "us", two-letter storefront code) or the numeric format of the IDs, leaving half the parameters to inference.

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 states a specific resource and scope: batch 'App listing summaries' for up to 50 IDs, with unavailable apps omitted. This makes the batch-by-ID nature distinguishable from siblings like search_app_store or list_apps, though those alternatives are never named.

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

Usage Guidelines3/5

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

Usage is only implied: the 50-ID cap and the ID-keyed input signal 'use this when you already have app IDs.' There is no explicit when-to-use, when-not-to-use, or pointer to list_apps / search_app_store for discovery instead of lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources