Temu Intelligence GB
Temu Category Research MCP
Find Temu categories to narrow your product research. Call the Temu Category Research API via REST or MCP with your Nexscope API key.
Temu Category Research 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. Find Temu Categories To Narrow Your Product Research
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Show the available results and clearly identify missing information.
2. Continue The Results Within A Page Limit
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Start at [my selected page] and return [my requested page size] within the documented limits. Ask before requesting another page and do not describe one page as the complete dataset.
3. Prioritize The Results For Review
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Prioritize [my chosen ranking metric] in [my chosen order]. Keep the ranking limited to the selected filters and reporting period.
4. Find Matches By Total Units Sold
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Limit results to [my chosen total units sold range]. Keep the lower and upper bounds consistent and show only the matching records.
5. Find Matches By Product Count
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Limit results to [my chosen product count range]. Keep the lower and upper bounds consistent and show only the matching records.
6. Find Matches By Store Count
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Limit results to [my chosen store count range]. Keep the lower and upper bounds consistent and show only the matching records.
7. Find Matches By Average Price
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Limit results to [my chosen average price range]. Keep the lower and upper bounds consistent and show only the matching records.
8. Find Matches By Total Sales Amount
Prompt: Find Temu categories to narrow your product research for [search phrase] in [target marketplace]. Limit results to [my chosen total sales amount range]. Keep the lower and upper bounds consistent and show only the matching records.
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_category_searchhttps://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-category-search-1",
"method": "tools/call",
"params": {
"name": "nexscope_geekbi_temu_category_search",
"arguments": {
"keyword": "pets",
"page": 1,
"regionId": 211,
"size": 3
}
}
}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 from sites[].regionId; never siteId. Example: 211 |
page | integer | optional | Page number. Example: 1 |
size | integer | optional | Items per page; page times size must not exceed 10000. Example: 3 |
keyword | string | optional | User keyword; preserve the supplied language. Example: pets |
sort | string | optional | Confirmed provider sort field; omit when unnecessary. |
order | string | optional | Sort direction, case-insensitive. |
dsrMin | number | optional | Lower bound for dsr; minimum must not exceed maximum. |
dsrMax | number | optional | Upper bound for dsr; minimum must not exceed maximum. |
totalSoldMin | integer | optional | Lower bound for totalSold; minimum must not exceed maximum. |
totalSoldMax | integer | optional | Upper bound for totalSold; minimum must not exceed maximum. |
itemCountMin | integer | optional | Lower bound for itemCount; minimum must not exceed maximum. |
itemCountMax | integer | optional | Upper bound for itemCount; minimum must not exceed maximum. |
mallCountMin | integer | optional | Lower bound for mallCount; minimum must not exceed maximum. |
mallCountMax | integer | optional | Upper bound for mallCount; minimum must not exceed maximum. |
avgPriceMin | number | optional | Lower bound for avgPrice; minimum must not exceed maximum. |
avgPriceMax | number | optional | Upper bound for avgPrice; minimum must not exceed maximum. |
totalSalesMin | number | optional | Lower bound for totalSales; minimum must not exceed maximum. |
totalSalesMax | number | optional | Upper bound for totalSales; minimum must not exceed maximum. |
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 |
total | integer | optional | Number of hits; possibly capped at 10,000 |
regionId | integer | optional | Actual query area |
columns | array | optional | Render column definitions, not business results |
items | array | optional | Category results; business fields may be missing or `null` |
parentCatId | integer | optional | When omitted, the top category is returned; when the known `catId` is passed, the direct child level is returned |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Find Temu categories to narrow your product research. Use “pets”.
Illustrative Response Explanation
The illustrative result contains no matching records. There is no product or performance comparison to make from this result; an empty response does not prove that the market has no matching items.
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-category-search-example",
"method": "tools/call",
"params": {
"name": "nexscope_geekbi_temu_category_search",
"arguments": {
"keyword": "pets",
"page": 1,
"regionId": 211,
"size": 3
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "geekbi-temu-category-search-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"items\":[]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"items": []
}
},
"isError": false
}
}