Skip to main content
Glama

search_reviews

Read-only

Find relevant app reviews via plain-language semantic matching, then filter by category or app version to locate specific feedback and complaint patterns.

Instructions

Semantic search over reviews, optionally filtered by category and app version. Returns review ids, ratings, versions, dates, classification and (untrusted) text.

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": "<app>",
      "query": "<query>"
    },
    "name": "search_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesGame slug, e.g. critical-strike.
limitNo
queryYesWhat to look for, in plain words.
versionNoOnly reviews of this app version.
categoryNoOnly reviews with this category.

Output Schema

NameRequiredDescriptionDefault
appYes
queryYes
resultsYes
versionYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, yet the description still adds real value by enumerating the returned fields and flagging the review text as untrusted — a meaningful prompt-injection caution absent from structured data. It omits ranking/ordering behavior and how limit interacts with result quality, which keeps it short of a 5.

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, no filler: the retrieval mode and filters come first, the return contract second. Nothing is repeated from the tool name and every clause carries information.

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 an output schema present, the return values need not be explained, yet the description still summarizes them; required parameters and the app slug are covered by the schema. The main residual gap for a search tool is result ordering/relevance behavior and result-set size limits, which are not described.

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 80%, so parameters are already well documented (app slug, plain-words query, version and category filters). The description only restates that category and version are optional filters, adding no syntax, matching, or ranking semantics beyond the schema; baseline 3 is appropriate.

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?

States a specific verb and resource ('Semantic search over reviews') plus the optional filter dimensions, which is far more informative than the bare name. It does not, however, distinguish this from siblings such as 'ask' or 'top_issues', so an agent must infer the boundary between free-form semantic retrieval and the more analytical siblings.

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: 'semantic search' plus a plain-words query suggests exploratory lookup of individual reviews, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. The agent gets a reasonable hint but no routing rule.

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