Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_shop_products

Retrieve a US TikTok Shop store's details and first page of up to 20 products in default order, including whether more products exist.

Instructions

tiktok-shop: Shop Products. GET /v1/tiktok/shop/products. A US TikTok Shop store's details (shopInfo) and its first page of products (up to 20) in the store's default order. First page only: cursor is always null, and has_more says whether the store has more. An empty page costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when products 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

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": {
      "url": "<url>"
    },
    "name": "tiktok_shop_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe TikTok Shop store URL.
cursorNoNot accepted: only the first page is available, so responses carry cursor null.
regionNoOnly US is supported.
sort_byNoOnly top, the store's default order, is accepted.

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?

With no annotations, the description carries the full burden and does a lot: cursor is always null, has_more flags more products, results are capped at 20, cache hits are free, and credit cost is broken out per outcome. It loses a point because the final sentence about not-found/empty charging arguably conflicts with the earlier 'Costs 0 credits when products is empty,' leaving the actual billing on an empty result ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded, but roughly half the text is a repetitive credit-cost breakdown spread over four sentences, and the closing sentence muddies rather than clarifies the pricing rule. Trimming the cost enumeration would make the definition materially tighter.

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?

For a tool with no output schema and no annotations, the description covers return shape (shopInfo + products, max 20), pagination semantics, accepted inputs, and cost model, which is enough to call it correctly. Missing details like auth/prerequisite requirements or the fields inside each product keep it from being fully complete.

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 100%, so every parameter is already documented in the schema, and the description adds little beyond it: it restates that cursor is always null and only the default sort is accepted. Baseline 3 is appropriate given the schema does the parameter-level work.

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 ('GET /v1/tiktok/shop/products'), the exact scope (a US TikTok Shop store), and precisely what comes back: shopInfo plus the first page of up to 20 products in the store's default order. It is clearly distinct from tiktok_product (single product) or tiktok_shop_product_reviews.

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 constraints are stated (US only, first page only, default order only), which implies when the tool fits, but there is no explicit guidance about alternatives such as tiktok_shop_search or tiktok_product for other needs. The agent must infer the 'when' from the limits rather than being routed.

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