Amazon Marketplace Intelligence
Amazon Category Lookup MCP
Find Amazon category IDs by marketplace or category name. Call the Amazon Category Lookup API via REST or MCP with your Nexscope API key.
Amazon Category Lookup 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. Browse Amazon Categories
Prompt: Show the categories below Amazon category [PARENT_CATEGORY_ID] in [MARKETPLACE].
2. Find A Category By Name
Prompt: Find Amazon category labels matching [CATEGORY_NAME] in [MARKETPLACE] and show the returned category paths so I can choose the right one.
3. Browse A Historical Category Tree
Prompt: Browse child categories beneath [parent category] in [marketplace] using the snapshot for [year and month]. Preserve category identifiers so I can compare that snapshot with the current category tree.
What You Need to Provide
Replace the bracketed placeholders with your own research inputs. Keep source estimates, reporting periods and missing information explicit.
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_amazon_category_lookuphttps://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": "amazon-category-lookup-1",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_category_lookup",
"arguments": {
"marketId": "1",
"nodeId": "0",
"operation": "lookup"
}
}
}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 |
|---|---|---|---|
operation | string | optional | lookup (default) or like. Example: lookup |
marketId | string | optional | Amazon marketplace or site identifier. Example: 1 |
nodeId | string | optional | Parent category node identifier. Example: 0 |
table | string | optional | Optional upstream category table selector. Example: nodes |
nodeLabel | string | optional | Category label required by operation=like. Example: Electronics |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | required | Data value used by this API operation. |
msg | string | null | required | Msg value used by this API operation. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | required | Trace id value used by this API operation. |
ts | string | required | Epoch milliseconds. |
Any of option 1
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.costTime | integer | optional | Execution time reported by the upstream provider. Example: null |
data.costToken | integer | optional | Provider-reported token cost. Example: 150 |
data.data | array | optional | Amazon category node records. Example: [] |
data.data[] | object | required | Amazon category node records. |
data.data[].nodeId | string | optional | Category node identifier. Example: 172282 |
data.data[].nodeLabel | string | optional | Category label. Example: Electronics |
data.data[].parentNodeId | string | optional | Parent node identifier. Example: 0 |
data.dataSnapshotMonth | string | optional | Data snapshot month returned by the upstream provider. Example: null |
data.page | integer | optional | Current page returned by the upstream provider. Example: null |
data.pageItemCount | integer | optional | Item count on the current page returned by the upstream provider. Example: null |
data.pageSize | integer | optional | Page size returned by the upstream provider. Example: null |
data.sourceTool | string | optional | Provider-specific source tool name. Example: null |
data.sourceType | string | optional | Provider-specific source platform type. Example: null |
data.title | string | optional | Provider-specific response title. Example: null |
data.total | integer | optional | Number of returned category nodes. Example: 1 |
data.totalPage | integer | optional | Total page count returned by the upstream provider. Example: null |
data.type | string | optional | Provider-specific render or payload type. Example: null |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Show the top-level Amazon categories for market 1.
Illustrative Response Explanation
The illustrative response contains one category: Electronics, node 172282, under parent node 0. Use that node to request its child categories.
About this sample: Illustrative example only. Names, identifiers and numbers are fictional; no live tool call was made. Your results depend on your account, inputs and available data.
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": "amazon-category-lookup-example",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_category_lookup",
"arguments": {
"marketId": "1",
"nodeId": "0",
"operation": "lookup"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "amazon-category-lookup-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"data\":[{\"nodeId\":\"172282\",\"nodeLabel\":\"Electronics\",\"parentNodeId\":\"0\"}],\"total\":1},\"cost\":\"0\",\"time\":\"2026-01-01 00:00:00\",\"traceId\":null,\"ts\":\"1767225600000\"}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"data": [
{
"nodeId": "172282",
"nodeLabel": "Electronics",
"parentNodeId": "0"
}
],
"total": 1
},
"cost": "0",
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "1767225600000"
},
"isError": false
}
}