Skip to main content
Glama

FoxAPIs data sources

Google Play app

googleplay_app
Read-onlyIdempotent

A Google Play listing: rating, ratings and installs, price, category, last update and content rating, from its link. Costs 8 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "url": "<url>"
    },
    "name": "googleplay_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://play.google.com/store/apps/details?id=com.instagram.android"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, but the description adds genuinely non-structured behavior: a cost of 8 credits per call, a no-charge guarantee for empty answers, and a required FoxAPIs key. That billing/auth detail is exactly the context annotations cannot convey; only rate limits and failure modes are missing.

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?

Two sentences, zero waste: the returned fields are front-loaded, then the cost/auth constraints. Every clause earns its place and nothing is repeated from the title.

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 one-parameter read tool with annotations and no output schema, the definition covers returned fields, cost model, and auth requirement. Minor gaps remain around failure behavior for invalid or region-restricted URLs and whether results are cached.

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 the single url parameter already carries a concrete Play Store example. The phrase 'from its link' confirms the parameter must be a listing URL, but adds no format, validation, or locale/slug nuance beyond the schema.

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 resource ('A Google Play listing') and enumerates exactly what it returns: rating, ratings and installs, price, category, last update, content rating. 'Google Play' also implicitly separates it from the sibling appstore_app. It lacks an explicit retrieval verb, which keeps it from a 5.

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?

Usage is only implied by 'from its link' – an agent can infer that a Play Store URL is the input, but the description never says when to choose this over appstore_app or any other store-listing tool, nor any when-not condition.

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