Ozon Intelligence MP
Ozon Product Search MCP
Search Ozon products by Russian keyword or SKU and return product ID, title, brand, and seller data for discovery. Available via REST API or MCP.
Ozon Product Search 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 Ozon Products By Keyword Or SKU
Prompt: Find Ozon products by keyword or SKU for [search phrase]. Show the available results and clearly identify missing information.
2. Find Ozon Products By Keyword Or SKU By Product IDs
Prompt: Find Ozon products by keyword or SKU using [product IDs]. Keep the returned results tied to that input and do not infer matches that were not returned.
3. Review A Specific Reporting Period
Prompt: Find Ozon products by keyword or SKU for [search phrase]. Use [my chosen reporting period] and show the period with the returned figures. Keep dated snapshots distinct from current data.
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_ozon_product_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": "ozon-product-search-1",
"method": "tools/call",
"params": {
"name": "nexscope_ozon_product_search",
"arguments": {
"endDate": "2026-01-31",
"keyword": "ΠΊΡΠΎΡΡΠΎΠ²ΠΊΠΈ",
"startDate": "2026-01-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 |
|---|---|---|---|
keyword | string | optional | Russian search keyword, e.g., ΠΊΡΠΎΡΡΠΎΠ²ΠΊΠΈ (running shoes); provide keyword or productIds Example: ΠΊΡΠΎΡΡΠΎΠ²ΠΊΠΈ |
productIds | array | optional | List of Ozon product SKUs (integer or string) Example: [] |
startDate | string | optional | Statistics start date, format YYYY-MM-DD; defaults to one year ago if empty; latest is yesterday Example: 2026-01-01 |
endDate | string | optional | Statistics end date, format YYYY-MM-DD; defaults to yesterday if empty; latest is yesterday Example: 2026-01-01 |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | string | optional | Return code (string), `"200"` indicates success |
msg | string | optional | Message; `ok` on success, error description on failure |
total | integer | optional | total hits |
products | array | optional | Product list |
columns | array | optional | Render column definition |
costTime | integer | optional | Interface time (milliseconds) |
costToken | integer | optional | Amount of Token consumed |
type | string | optional | response type |
productId | integer | optional | SKU ID |
title | string | optional | Product name (Russian) |
productPageUrl | string | optional | Product page URL |
imageUrl | string | optional | Main image URL |
brand | string | optional | Brand name |
brandId | integer | optional | Brand ID |
sellerName | string | optional | Seller name |
sellerId | integer | optional | Seller ID |
sourceType | string | optional | Data source identifier, always `ozon` |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Find Ozon products by keyword or SKU. Use βΠΊΡΠΎΡΡΠΎΠ²ΠΊΠΈβ.
Illustrative Response Explanation
The illustrative result shows title: Example product; product id: 10; seller id: 10. 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": "ozon-product-search-example",
"method": "tools/call",
"params": {
"name": "nexscope_ozon_product_search",
"arguments": {
"endDate": "2026-01-31",
"keyword": "ΠΊΡΠΎΡΡΠΎΠ²ΠΊΠΈ",
"startDate": "2026-01-01"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "ozon-product-search-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"products\":[{\"title\":\"Example product\",\"productId\":10,\"sellerId\":10}]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"products": [
{
"title": "Example product",
"productId": 10,
"sellerId": 10
}
]
}
},
"isError": false
}
}