Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_shop_search

Searches TikTok Shop US results for a keyword and returns up to about 25 products from the first page only.

Instructions

tiktok-shop: Shop Search. GET /v1/tiktok/shop/search. Products on TikTok Shop's US results page for a keyword (up to about 25). First page only. A keyword with no results page returns 404 at 0 credits, and 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": {
      "query": "<query>"
    },
    "name": "tiktok_shop_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOnly 1 is accepted: later pages are not available.
queryYesKeyword to search for, such as shoes or running shoes.
regionNoOnly US is supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose the most consequential trait: the credit cost model, including that 404/empty/error/cache-hit responses cost nothing and only a successful non-empty result costs a credit. It stops short of covering auth requirements, retry behavior for blocked requests, or the shape of the returned product records.

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 purpose and scope are front-loaded in the first two sentences, which is good. The remainder is a bloated, self-repeating cost paragraph where 'costs 0 credits' is restated three separate ways and the final sentence about 'published cost' is vague filler that dilutes the concrete pricing facts.

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?

With no output schema and no annotations, the description must cover both behavior and returns; it partly does by indicating the output is a list of up to ~25 products and by spelling out the cost profile. It never describes the fields of a returned product or what an agent should do on the 404/empty cases it mentions, so it is adequate but not complete for a search tool.

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%, and the schema already states that only page 1 is accepted and that only US is supported, so the description adds essentially no new parameter meaning and merely echoes the 'first page only' constraint. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Products on TikTok Shop's US results page for a keyword') and bounds the result set ('up to about 25'), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from the sibling tiktok_shop_products, leaving the agent to infer the difference between searching a results page and listing products.

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?

Useful limits are stated: keyword-based search, first page only, US results page. However there is no explicit when-to-use / when-not-to-use guidance, and no sibling is named as an alternative for paginated or non-search product retrieval, so the routing is implied rather than directed.

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