Skip to main content
Glama

List TikTok Shop product reviews

tiktok_product_reviews_list
Read-only

List buyer reviews for a TikTok Shop product by product id. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic TikTok Shop product detail page URL for the product whose reviews should be listed.
linkNoAlias for `url`. Prefer `url`.
pageNo1-based review page number. Omit to request the first page.
pathNoAlias for `url`. Prefer `url`.
trimNoIgnored if this tool does not support it.
limitNoIgnored if this tool does not support it.
offsetNoIgnored if this tool does not support it.
regionNoOptional country or region code for the product review catalog. When omitted, the default catalog region applies.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
tweetIdNoAlias for `url`. Prefer `url`.
pageSizeNoIgnored if this tool does not support it.
tweetUrlNoAlias for `url`. Prefer `url`.
tweet_idNoAlias for `url`. Prefer `url`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
permalinkNoAlias for `url`. Prefer `url`.
productIdNoTikTok Shop product identifier. Provide this instead of `url` when you already know the product id.
tweet_urlNoAlias for `url`. Prefer `url`.
maxResultsNoIgnored if this tool does not support it.
max_resultsNoIgnored if this tool does not support it.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / link / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / link / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `url`. Prefer `url`."
      +}
    • addedInput schema / properties / permalink / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / permalink / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / tweetId / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetId / type
      Removed value: -"string"
    • addedInput schema / properties / tweetUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetUrl / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_id / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_url / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_url / type
      Removed value: -"string"
  2. Changed6 schema fields changed
    • addedInput schema / properties / link
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / permalink
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetId
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetUrl
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_id
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_url
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  6. Changed4 schema fields changed
    • removedInput schema / properties / page / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +1
    • addedInput schema / properties / page / type
      Added value: +"integer"
  7. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the tool's read-only nature is covered. The description adds the cursor-based pagination behavior ('use cursor when paginated'), which is useful. However, it does not disclose other behavioral traits like auth requirements, rate limits, or the structure of the returned list. Since the description adds only minimal behavior beyond annotations, a 3 is appropriate.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the primary purpose and includes the key pagination note. There is zero waste, and it is structured to give the agent immediate understanding. It does not repeat schema information unnecessarily.

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?

The tool has no output schema, so the description should explain the return format more thoroughly. It only says 'Returns a list (use cursor when paginated)', which is a start but does not describe what fields a review contains or how pagination works beyond using a cursor. With many parameters and a complex alias scheme, the description does not fully help an agent decide which parameters to supply (e.g., url vs productId, or region). The description is adequate for a simple read tool but leaves gaps in behavioral details and parameter selection.

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 the baseline is 3. The description does not add meaning beyond the schema; it mentions 'by product id' which aligns with the productId parameter, but the schema already documents this. The many alias parameters (link, path, tweetId, etc.) are described in the schema as aliases for url, but the description does not help clarify their redundancy or usage. It does not compensate for the schema's generic descriptions.

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 clearly states the verb ('List'), the resource ('buyer reviews for a TikTok Shop product'), and the key identifier ('by product id'). It also mentions the pagination behavior. This distinguishes it from sibling tools like tiktok_product_get or tiktok_shop_products_list, which have different purposes. The description is specific and unambiguous.

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?

The description implies the tool is for listing reviews of a specific product, but it does not explicitly mention when to prefer this tool over alternatives or when not to use it. For example, it doesn't note that tiktok_shop_products_list is for browsing products, or that tiktok_product_get gives product details. The usage is implied but not clarified with exclusions or alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.