Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

target_reviews

Read-only

Returns paginated written reviews for a Target item. Pagination is zero-based and page 50 is the upstream maximum. tcin: Required. Numeric Target item id (TCIN). per_page: Optional. Results per page, 1-25. Defaults to 25. Use target_questions to list Target product questions and answers.

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": {
      "tcin": "<tcin>"
    },
    "name": "target_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional. Zero-based page, 0-50. Defaults to 0.
tcinYesRequired. Numeric Target item id (TCIN).
per_pageNoOptional. Results per page, 1-25. Defaults to 25.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 meaningful behavioral constraints beyond that: pagination is zero-based and page 50 is the upstream hard maximum, plus the 1-25 per_page bounds, which tells the agent about a real limit it could otherwise trip.

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?

Purpose is front-loaded, followed by pagination behavior, parameter notes, and the sibling reference. It is efficient and orderly, though the parameter sentences duplicate the schema almost verbatim and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value detail is unnecessary, and the description covers the key call-time facts: what it returns, the pagination model and ceiling, and the required id. Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so the schema already documents tcin, page (0-50, default 0), and per_page (1-25, default 25). The description largely restates those values, including the same page-50 ceiling and per_page range, adding no new syntax or semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns paginated written reviews for a Target item') and explicitly names the sibling target_questions as a different resource type, so an agent can distinguish it from the questions tool without opening either schema.

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?

The description points to target_questions for a related-but-different need, which is a partial routing hint, but it never states when to use target_reviews versus other item-overview siblings like target_product or when reviews are the right choice. Usage is implied by the resource name rather than stated.

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

All Crawlora MCP 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