Skip to main content
Glama

probe_keyword

Query Apple App Store search and review data by keyword to identify top competitors, compare pricing and ratings, and surface verbatim 1–3 star complaints.

Instructions

[FREE] Query Apple App Store iTunes Search API + Customer Reviews RSS for a keyword. Returns top 5 competitors (pricing, rating, review count, vulnerability score) and verbatim 1-3 star user complaints.

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": {
      "keyword": "<keyword>"
    },
    "name": "probe_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax competitors to return (1-10)
countryNo2-letter App Store storefront code (e.g. 'us', 'cn', 'jp')us
keywordYesSearch keyword, e.g. 'teleprompter' or '提词器'
use_fixtureNoUse deterministic offline fixture dataset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real context: the tool is free, it hits two external Apple endpoints, and it returns a bounded set of competitors plus verbatim review quotes. It omits operational behavior an agent would benefit from — network dependency/latency, failure or empty-result modes, rate limiting, and that use_fixture toggles offline behavior.

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 dense sentences with the '[FREE]' tag front-loaded, an explicit source stack, and a compact statement of the return payload. Nothing is redundant and the most decision-relevant facts (free, source, output shape) come first.

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 4-parameter, no-output-schema, no-annotation tool, the description covers what it queries and roughly what comes back, which is what an agent needs to select and call it. It stops short of describing error/empty handling or the unit of the 'vulnerability score', which is the main remaining gap.

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 description coverage is 100%, so every parameter is already documented in the schema; the description only reinforces 'keyword' and the top-5 default for limit. It adds no meaning about country coverage semantics or when to set use_fixture, so 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 ('Query Apple App Store iTunes Search API + Customer Reviews RSS for a keyword') and even summarizes the payload (top 5 competitors with pricing, rating, review count, vulnerability score plus verbatim 1-3 star complaints). It does not explicitly contrast itself with compare_matrix or generate_battlecard, so an agent must infer that this is the raw data-gathering step, which keeps it below 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 Guidelines3/5

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

Usage is only implied: the phrasing suggests this is the entry point that feeds competitor analysis, and the sibling names imply a pipeline, but there is no explicit 'use this when you need raw competitor data; use compare_matrix when you need a side-by-side'. No exclusions or prerequisites are stated.

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