SiteCheck Shop & Social

Reviews of a Target product by TCIN: rating statistics

ecommerce_target_reviews

Read-only

Reviews of a Target product by TCIN (the number after A- in a target.com product URL): rating statistics (average, count, 1-5 star distribution, % recommended, review and question counts) and reviews with rating, title, text, recommended and verified-purchase flags, helpful votes, photo count and date. Sort by most recent, most helpful, highest or lowest rating; optional verified-only. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "ecommerce_target_reviews"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number from 1 (default 1)
`sort`	No	recent (default), helpful, highest or lowest
`tcin`	Yes	Target product ID (TCIN), e.g. 1012279797 (required)
`limit`	No	Reviews per page, 1 to 50 (default 10)
`verified`	No	true for verified purchases only

Output Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`tcin`	No
`count`	No
`source`	No
`reviews`	No
`checkedAt`	No
`productUrl`	No
`statistics`	No
`totalReviews`	No
`verifiedOnly`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful operational context beyond that: the exact pricing model ($0.002 USDC per successful call via x402 on Base, Solana, or Arc) and that failed calls are not charged. This is the kind of billing/behavioral detail annotations cannot express.

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?

The description is a single dense paragraph that front-loads the resource and then covers return fields, sorting, and pricing. Every sentence carries information, though it is packed and could be slightly easier to scan with separators.

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?

The output schema handles return structure, and the annotations cover safety, so the description need not explain response shapes. It nonetheless supplements with pricing/payment details and TCIN identification. The only minor gap is that pagination behavior is left entirely to the schema, but that is adequately documented there.

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%, so the baseline is 3. The description still adds value by clarifying that TCIN is the number after A- in a target.com URL and by restating the sort modes in natural language (most recent, most helpful, highest/lowest rating) plus the verified-only filter, which helps an agent map intent to parameters.

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?

The description states a specific resource and scope: reviews and rating statistics for a Target product identified by TCIN. It enumerates the returned data (average, count, star distribution, % recommended, review attributes) so an agent can distinguish it from any sibling retailer tool without opening the schema.

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?

It clearly establishes the use context: you need a Target product's reviews and rating statistics, and it explains how to obtain the TCIN (the number after A- in a product URL). It also states supported sort modes and the optional verified-only filter. No explicit when-not-to-use or alternative is named, but the sibling set contains no competing Target review tool, so context is sufficient.

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

All SiteCheck Shop & Social tools Inspect

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

Need Help?