Ozon Intelligence MP
Ozon Intelligence MP: ozon/product Trend API
Ozon Intelligence MP: ozon/product Trend API.
MCP tool name
nexscope_data_mp_ozon_product_trendMCP 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-mp-ozon-product-trend-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_mp_ozon_product_trend",
"arguments": {
"endDate": "2025-03-31",
"includeSearchStats": true,
"productId": 1786874757,
"startDate": "2025-03-01"
}
}
}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 |
|---|---|---|---|
productId | integer | required | Ozon product SKU Example: {} |
startDate | string | optional | Statistics starting date, `YYYY-MM-DD`; data delay T-1, the latest day can be selected Example: {} |
endDate | string | optional | Statistics end date, `YYYY-MM-DD`; data delay T-1, the latest available is yesterday Example: {} |
includeFbs | boolean | optional | Whether to include FBS data Example: {} |
includeSearchStats | boolean | optional | Whether it comes with search position/visibility; some tracks do not support it Example: {} |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | string | optional | Return code (string), `"200"` indicates success Example: {} |
errcode | integer | optional | Return code (integer), `200` indicates success Example: {} |
total | integer | optional | Number of data points per day (number of window days) Example: {} |
data | array | optional | List of daily data points Example: {} |
columns | array | optional | Render column definition Example: {} |
costTime | integer | optional | Interface time (milliseconds) Example: {} |
costToken | integer | optional | Amount of Token consumed Example: {} |
type | string | optional | response type Example: {} |
date | string | optional | Date, `YYYY-MM-DD` Example: {} |
hasData | boolean | optional | Whether there is data on that day; `false` indicates the missing day, which is different from `sales=0` Example: {} |
price | number | optional | Selling price on the day Example: {} |
oldPrice | number | optional | Original price before discount on the day Example: {} |
ozonCardPrice | number | optional | Ozon Card price (Ozon official bank card discount price) Example: {} |
discount | integer | optional | Discount, percentage integer 0-100 Example: {} |
currency | string | optional | Currency symbol (such as `₽` / `$` / `€`) Example: {} |
sales | integer | optional | Sales volume on the day (pieces) Example: {} |
balance | integer | optional | FBO warehouse inventory on the day (pieces) Example: {} |
rating | number | optional | Rating, value 0-5 Example: {} |
comments | integer | optional | Number of comments Example: {} |
isBestseller | boolean | optional | Whether there is a "best selling" mark on that day Example: {} |
isNew | boolean | optional | Whether there is a "new product" mark on that day Example: {} |
Examples
Example arguments
{
"endDate": "2025-03-31",
"includeSearchStats": true,
"productId": 1786874757,
"startDate": "2025-03-01"
}Example structuredContent
{
"code": 0,
"cost": "-1",
"data": {},
"msg": null,
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "0"
}