Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_product

Retrieve details for a US TikTok Shop product from its URL, including product information for a given listing. Use it when you need product data from a TikTok Shop link.

Instructions

tiktok-shop: Product Details. GET /v1/tiktok/product. Get details for a TikTok Shop product. US products only. Costs 1 credit when it succeeds. 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_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the product to get details for.
regionNoOnly US is supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden, and it delivers a genuinely useful disclosure: the credit is charged only on success, while errors, blocked, timed-out, invalid requests and cache hits cost nothing, and not-found billing follows the published cost. What it omits is any statement of what the returned product detail contains and whether any authorization or rate constraints apply, which matters since there is no output schema.

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 scope are front-loaded, and the billing sentence is dense but carries real decision-relevant information. The leading "tiktok-shop: Product Details. GET /v1/tiktok/product." and the following "Get details for a TikTok Shop product." are partially redundant, a minor waste in an otherwise tight description.

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

Completeness3/5

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

This is a simple two-parameter read, and the geographic constraint and cost model are well covered. The remaining gap is the absence of any indication of what the product detail payload includes, which is more consequential here because no output schema exists to fill that hole.

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 both url and region are already fully documented in the schema, including region's "Only US is supported" note. The description's "US products only" restates that same constraint rather than adding new meaning, so the baseline of 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource ("Get details for a TikTok Shop product") plus the underlying endpoint GET /v1/tiktok/product, so the agent knows exactly what it returns. It does not distinguish itself from nearby siblings such as tiktok_shop_products or tiktok_shop_product_reviews, so the agent must infer that this is the single-product lookup rather than a listing or review fetch.

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?

"US products only" establishes a hard eligibility constraint, and the required url parameter implies the tool is used when you already have a product URL. However, there is no explicit guidance on when to choose this over tiktok_shop_products (discovery) or when product reviews are the better target, leaving the routing decision implicit.

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