Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok Shop product

tiktok_product_get
Read-onlyIdempotent

Retrieve TikTok Shop product details from a public product page URL to inspect pricing, availability, and listing information for a specific item.

Instructions

Get details for a TikTok Shop product by product id. Requires url.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_product_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public TikTok Shop product detail page URL for the product to retrieve.
regionNoOptional country or region code for the product catalog. When omitted, the default catalog region applies.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
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. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, and the description does not contradict them. Beyond noting the required URL, it adds no auth, error, pagination, region-default, or return-content context.

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?

The description is two short, front-loaded sentences with no filler. "Requires `url`" is somewhat redundant with the schema and the product-id phrasing is imprecise, but the structure is efficient.

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?

For a simple read tool with rich annotations and full schema coverage, the definition is mostly sufficient. Because there is no output schema, it could say more about what product details are returned or how errors and region defaults behave.

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 url, region, context, llm_model, and conversation_id are already documented in the schema. The description's "product id" wording does not quite match the url parameter and it adds no extra meaning for the other parameters, so the baseline of 3 applies.

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?

The description names a specific verb and resource: getting details for a single TikTok Shop product. It distinguishes this from list/search siblings by focusing on one product, though it says "by product id" while the schema requires a product URL, which is a slight inconsistency.

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?

It implies use when you have a product identifier and states the URL prerequisite. However, it does not explicitly route between this tool and tiktok_shop_products_list or tiktok_shop_products_search, nor does it say when not to use this tool.

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