Temu Intelligence GB
Temu Intelligence GB: temu/keyword Search API
Temu Intelligence GB: temu/keyword Search API.
MCP tool name
nexscope_data_gb_temu_keyword_searchMCP endpoint
https://api.nexscope.ai/mcpJSON-RPC method
tools/callAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxIf authentication fails, ask the user to open API Access and copy a valid key.
Call this MCP tool
Initialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "data-gb-temu-keyword-search-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_gb_temu_keyword_search",
"arguments": {
"catIds": [
27011
],
"keyword": "dress",
"order": "desc",
"page": 1,
"regionId": 211,
"size": 20,
"sort": "totalSold",
"totalSoldMin": 1000
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
regionId | integer | optional | Temu region ID, taken from site list `sites[].regionId` Example: {} |
page | integer | optional | Page number Example: {} |
size | integer | optional | Quantity per page; `page * size` must not exceed 10000 Example: {} |
order | string | optional | Sorting direction; no default value for gateways Example: {} |
sort | string | optional | Sorting fields; only use fields that the interface has confirmed to support Example: {} |
keyword | string | optional | Chinese or English keywords; should not silently translate or replace user input Example: {} |
catIds | integer[] | optional | Multiple IDs match any category Example: {} |
firstOnSaleTimeMin | string | optional | Minimum minimum shelf time for related products Example: {} |
firstOnSaleTimeMax | string | optional | The upper limit of the earliest shelf time of related products Example: {} |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
errcode | integer | optional | Business status; success is `200` Example: {} |
errmsg | string | optional | Status text; `ok` on success Example: {} |
total | integer | optional | Number of hits; possibly capped at 10,000 Example: {} |
regionId | integer | optional | Actual query area Example: {} |
columns | array | optional | Render column definitions, not business results Example: {} |
items | array | optional | Keyword results; business fields may be missing or `null` Example: {} |
Examples
Example arguments
{
"catIds": [
27011
],
"keyword": "dress",
"order": "desc",
"page": 1,
"regionId": 211,
"size": 20,
"sort": "totalSold",
"totalSoldMin": 1000
}Example structuredContent
{
"code": 0,
"cost": "-1",
"data": {},
"msg": null,
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "0"
}