Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

target_reviews

Fetch Target product reviews by numeric tcin, including ratings, text, author, votes, and flags. Paginate zero-based pages up to 50, with 1-25 reviews per page.

Instructions

List Target product reviews. Lists written reviews for a Target item given by its numeric tcin. Each review has its rating, title, text, author, submission time, helpful votes, and verified and syndicated flags. page is zero-based and stops at 50; per_page runs 1 to 25. The response gives total and total_pages.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page
tcinYesNumeric Target item id
per_pageNoReviews per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/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 well: it discloses the pagination behavior ('page is zero-based and stops at 50; per_page runs 1 to 25') and the returned fields. It omits auth/rate-limit context, but for a read-only list endpoint this is solid disclosure beyond what structured fields provide.

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 and identifier are front-loaded, and every sentence carries information. Minor redundancy in 'List Target product reviews. Lists written reviews...', but overall tight and well-ordered.

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?

No output schema exists, so the description must cover the return shape, and it does ('total and total_pages', plus the review fields). Pagination limits are stated. Sorting options and error behavior are absent, but nothing essential for calling the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), and the description adds value beyond it by supplying the actual bounds for page (zero-based, max 50) and per_page (1 to 25), which the schema only labels generically as 'Zero-based page' and 'Reviews per page'.

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+resource ('List Target product reviews') and immediately names the identifier ('given by its numeric tcin'). It is clearly distinguishable from siblings like target_product, target_questions, and target_categories, which cover different resources.

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 implies when to use it (fetching reviews for a known tcin) but never names an alternative or an exclusion condition. With no sibling-review tool, ambiguity is low, but guidance is only implicit rather than 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