Temu Intelligence GB
Temu Site List MCP
List available Temu markets for product research. Results come back as structured JSON. Call the Temu Site List API via REST or MCP with your Nexscope API key.
Temu Site List AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. List Available Temu Markets For Product Research
Prompt: List available Temu markets for product research. Show the available results and clearly identify missing information.
2. Prepare Market Identifiers For Product Research
Prompt: List available Temu markets for product research. Show the available results and clearly identify missing information. Show the site and region identifiers side by side with market names, language and currency. Mark the region identifier as the input for product detail research; do not substitute the site identifier.
3. Check Market Coverage For A Research Plan
Prompt: List the supported Temu sites and compare them with [my planned market names]. Show exact matching market names, region identifiers, languages and currencies, with unmatched or ambiguous names in a separate list. Do not treat an absent record as proof the marketplace itself does not operate there.
What You Need to Provide
Replace bracketed inputs with your own values. Use only the documented marketplace, period and input formats.
Returned estimates and rankings describe the selected data and period; missing values are not zero and a page of results is not the full market.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_geekbi_temu_site_listhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "geekbi-temu-site-list-1",
"method": "tools/call",
"params": {
"name": "nexscope_geekbi_temu_site_list",
"arguments": {}
}
}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
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
errcode | integer | optional | Business status; success is `200` |
errmsg | string | optional | Status text; `ok` on success |
sites | array | optional | Supported Temu sites |
total | integer | optional | Number of sites |
columns | array | optional | Render column definition |
siteId | integer / string | optional | Upstream internal ID, not used for product, category, keyword or store filtering |
regionId | integer | optional | Temu region ID accepted by other endpoints; should be a non-empty positive integer |
name | string | optional | Site name |
cnName | string | optional | Site Chinese name |
lang | string | optional | site language |
currency | string | optional | site currency |
extraFields | object | optional | Upstream extension field, may be missing |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
List available Temu markets for product research.
Illustrative Response Explanation
The illustrative result shows name: Example record. These figures describe only the shown record. Missing measures cannot be calculated from this example.
About this sample: Illustrative example with fictional records, not a live tool call. Identifiers, prices and counts are demonstration values.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Illustrative example with fictional data, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "geekbi-temu-site-list-example",
"method": "tools/call",
"params": {
"name": "nexscope_geekbi_temu_site_list",
"arguments": {}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "geekbi-temu-site-list-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"name\":\"Example record\"}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"name": "Example record"
}
},
"isError": false
}
}