Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apps_item

Retrieves a single stored iOS App Store or Google Play app record by its exact app_uid from a search result, returning the saved details as JSON.

Instructions

Get one stored app record. Retrieves one iOS App Store or Google Play app by its exact app_uid, as returned by datasets_apps_search.

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": {
      "app_uid": "<app_uid>"
    },
    "name": "datasets_apps_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_uidYesExact app_uid from a search result, e.g. ios:123456789

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. "Get one stored app record" implies a read-only lookup of a cached record, but it does not state return shape, whether missing uids error or return empty, or whether cross-platform uid prefixes change behavior. Adequate but thin for a tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the purpose and followed by the retrieval mechanism; no filler. Slightly redundant between the two sentences (both say it retrieves one app record).

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 single-parameter lookup with complete schema documentation and no output schema, the description covers what an agent needs to call it and where the identifier comes from. Only the return content and not-found behavior are unstated, which is a minor gap at this complexity.

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?

One parameter at 100% schema description coverage, so the schema already defines `app_uid` with an inline example (`ios:123456789`). The description's "exact `app_uid`" restates the schema's "Exact app_uid from a search result" rather than adding format, casing, or prefix rules beyond it.

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?

Specific verb and resource: "Get one stored app record" followed by "Retrieves one iOS App Store or Google Play app by its exact `app_uid`." This clearly separates a single-record lookup from the many list/search siblings, though differentiation is implied via the id provenance rather than stated as an explicit contrast.

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?

Gives a clear usage condition: the `app_uid` must come from a prior `datasets_apps_search` result, which tells the agent this is a follow-up call, not an entry point. No explicit when-not-to-use or statement of what to do if the uid is unknown or the record is missing.

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