Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_shop_product_reviews

Retrieve a US TikTok Shop product's first review page by URL or product ID, including up to five reviews, total count, and star breakdown.

Instructions

tiktok-shop: Product Reviews. GET /v1/tiktok/shop/product/reviews. Provide one of: url, product_id. The first page of a US TikTok Shop product's reviews (up to 5), with total_reviews and the star breakdown. First page only. A product with no reviews costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when product_reviews is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_shop_product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe product URL. Required if product_id is not provided.
pageNoOnly 1 is accepted: later pages are not available.
regionNoOnly US is supported.
product_idNoThe product id. Required if url is not provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 on the most consequential trait: detailed credit-cost behavior (0 when empty or on errors/cache hits, 1 on success). It also discloses the hard cap of 5 reviews and the first-page-only limit, though auth requirements and rate limits are unmentioned.

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 constraints are front-loaded, but there is some waste: 'First page only' repeats the earlier 'first page ... (up to 5)', and two cost sentences both say an empty result costs 0. The final not-found/cache sentence is convoluted and partially restates earlier cost rules.

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?

There is no output schema, and the description compensates by naming the returned fields (total_reviews and star breakdown) and the 5-review ceiling. Costs and input constraints are covered, so an agent has nearly everything needed to call it correctly, with only auth and failure-mode detail 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 url, page, region, and product_id are already fully documented including the either/or requirement. The description's 'Provide one of: url, product_id' only restates the schema, and it adds no syntax or format detail beyond it, so the baseline of 3 applies.

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 names a specific resource (a US TikTok Shop product's reviews) and pins down the exact scope: first page only, up to 5 reviews, returning total_reviews plus a star breakdown. Combined with the endpoint path, an agent can tell this apart from catalog/shop-search siblings without opening a 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 gives clear invocation constraints: supply either url or product_id, page must be 1, and region must be US. It does not name an alternative tool for later pages or non-US shops, so the agent gets strong 'how' guidance but no explicit 'when-not/use instead' routing.

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