Skip to content
Eden Engine

TikTok Shop Product Detail Lookup (by Product ID)

omnial/tiktok-shop-web-fetch-product-detail

Given a TikTok Shop product_id (and optional region), looks up that product on TikTok Shop's web storefront. Confirmed behavior: a product_id that fails the endpoint's own format check returns a validation object explaining why (`valid: false`, the echoed `product_id`, a bilingual message); a well-formed product_id that does not resolve to an existing listing returns an empty object `{}`, billed $0. Behavior for a product_id that resolves to a real, live listing (the product's own title, price, images, seller, etc.) was not captured in calibration and is unconfirmed.

activeper callv1
Provider
Web & Business Data Network
Category
tiktok-shop
Provider price
$0.0020475 per call
Latency p50 / p95
— / —
Success rate
—
Verified
—

Provider list price; Omnial MCP charges provider cost plus a platform markup on top.

Contract

input_schema.json
{
  "type": "object",
  "required": [
    "product_id"
  ],
  "properties": {
    "region": {
      "type": "string",
      "default": "SG",
      "examples": [
        "SG"
      ],
      "description": "Region code"
    },
    "product_id": {
      "type": "string",
      "examples": [
        "1732108663255959373"
      ],
      "description": "Product ID"
    }
  },
  "additionalProperties": false
}
output_schema.json
{
  "type": "object",
  "properties": {
    "valid": {
      "type": "boolean",
      "description": "Whether the given product_id passed the endpoint's own format check. Observed `false` for an out-of-range product_id (e.g. '0', bit_length=0, expected 50-64). Never observed `true` -- no fixture captured a product_id that both passed the format check and resolved to a real listing. Absent entirely on the empty not-found shape."
    },
    "message": {
      "type": "string",
      "description": "Bilingual (Chinese/English) explanation of why the given product_id was rejected, e.g. an out-of-range bit length. Only present on the validation-error shape observed."
    },
    "product_id": {
      "type": "string",
      "description": "Echoes back the product_id supplied in the request. Only present on the validation-error shape observed; absent on the empty not-found shape."
    }
  },
  "description": "The result object, as returned at routing.responseResultPath ($.output). Only two shapes have been observed: a malformed/out-of-range product_id returns `{valid, product_id, message}` describing why the ID was rejected; a syntactically valid but nonexistent product_id returns an empty object `{}` (billed $0). A genuinely found product's own detail fields (title, price, images, seller, etc.) were not captured by either fixture and are UNCONFIRMED -- this schema describes only the two observed shapes.",
  "additionalProperties": true
}

Pricing

Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.

Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.

ChargeRate
Per call
Flat, regardless of what comes back
$0.0020475
Cost basis
Not recorded

This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.

Updated
Sep 15, 2026