Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

Get app metadata

app_metrics_metadata
Read-only

Fetch the full store listing for one app (title, developer, ratings, category, metadata, whether it shows ads or sells in-app purchases, and their price range and the purchase items the store lists with prices) by its package id. If you only have the app name, call app_search first to resolve it. Costs 3 credits.

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": {
      "store": "<store>",
      "country": "<country>",
      "package": "<package>"
    },
    "name": "app_metrics_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
packageYesApp package / bundle id, e.g. "com.discord" (Android) or a numeric App Store id. If you only have the app name, call app_search first to resolve it.
force_updateNoBypass the cache and refetch from the store. Slower; use sparingly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds non-annotation context an agent genuinely needs: a cost of 3 credits, and the payload is a full listing including ad/IAP monetization signals. Nothing contradicts the annotations.

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?

Front-loaded with the operation and return contents, followed by the app_search fallback and the credit cost. It is a single dense sentence plus two short ones with no filler; the parenthetical field list is long but earns its place given there is no output schema.

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?

With no output schema, the description compensates by enumerating what comes back, and it discloses the cost and the name-to-package resolution path. Store/country requirements are left to the schema, which fully documents them, so nothing essential is missing.

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?

Schema coverage is 100% and each parameter (store enum, country ISO code, package, force_update cache bypass) is documented in the schema. The description only restates the package-id semantics, which duplicates the schema field text rather than adding new meaning; baseline 3 applies.

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 names a specific verb and resource ('fetch the full store listing for one app') and enumerates the returned fields (title, developer, ratings, category, ads/IAP, prices), so an agent knows exactly what it retrieves and keyed by package id. It doesn't explicitly contrast with the sibling app_metrics_metadata_batch, so it stops short of 5.

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

Usage Guidelines4/5

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

It gives a clear routing rule: if you only have the app name, call app_search first to resolve the package id. That is a concrete alternative and condition. It lacks any explicit 'when not to use' or a pointer to the batch sibling for multiple apps.

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

All AppmanAi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources