Skip to main content
Glama

Ozon Product Report Search

nexscope_ozon_product_report_search
Read-only

Nexscope Ozon product report search: filters Ozon products by multi-dimensional metrics including sales, revenue, sales/revenue growth rate, cart conversion rate, order conversion rate, price, rating, review count, QA count, variant count, page views, gross margin, return/cancellation rate, ad spend share, weight/volume, listing time, brand, seller, fulfillment method, and labels. Returns each product's SKU, title, price (RUB), sales, revenue, lost revenue, conversion rate, rating, reviews, brand, seller, fulfillment method, listing days/months, and complete product report fields. Use for Ozon product selection, competitor product analysis, best-seller mining, price/conversion band filtering. Trigger when the user mentions Ozon product report, Ozon product selection, Ozon product filtering, Ozon product analysis, Ozon best-selling products, Ozon competitor product analysis, Ozon product report, Ozon product screener, filter Ozon products by sales, Ozon best-seller mining, Nexscope Ozon product report. Also trigger when the intent is to filter Ozon products by multiple metrics and view product-level reports, even without explicitly mentioning Nexscope.

Input Schema

NameRequiredDescriptionDefault
drrNoAdvertising cost-share range: {min, max}; either bound may be omitted
tagNoTag word
uIdNoUser ID
pageYesNonempty pagination and sorting object: {page, pageSize, orders[]}. Omitted nested defaults are not inserted. Ranges accept optional finite bounds and require min <= max; numeric strings and optional null remain backend compatibility extensions.
skusNoSKU array (max 10), for precise lookup of specified products
brandNoBrand filter: {brandName: array<string>, type: integer}; type takes 0 include brand, 1 exclude brand, 2 unbranded
priceNoPrice range in RUB: {min, max}; either bound may be omitted
labelsNoLabel array, fixed options: 0 new product, 1 genuine product, 2 best seller
volumeNoVolume range in liters: {min, max}; either bound may be omitted. The supplier does not specify whether this measures the item or parcel.
weightNoWeight range in grams: {min, max}; either bound may be omitted. The supplier does not specify whether packaging is included.
keywordsNoKeyword array, filters by product title
memberIdNoMember ID (a unique member identifier; data is attributed to memberId)
variantsNoVariant-count range: {min, max}; either bound may be omitted
page.pageNoPage number, starting from 1, default 1
searchDateNoQuery date yyyy-MM-dd. Omit for a rolling last-30-days period; provide a date to query the preceding complete historical month (2026-04-01 selects March 2026), not month-to-date.
sellerNameNoSeller name array
categoryIdsNoCategory ID array (Nexscope category IDs, not category names)
fulfillmentNoFulfillment method array, fixed options: OZON, FBO, FBS, RFBS, FBP
grossMarginNoGross-margin range: {min, max}; either bound may be omitted
page.ordersNoSort rules, elements {field, direction}; direction takes DESC (descending) / ASC (ascending). field is a metric field in the response (e.g., sales, revenue, price, reviewRating, reviewCount, salesRate)
reviewCountNoReview-count range: {min, max}; either bound may be omitted
creationDateNoListing time filter (months), fixed options: 1 last 30 days, 3 last 90 days, 6 last 180 days, 12 last year, 24 last two years; no filtering if omitted
monthlySalesNoMonthly sales range: {min, max}; either bound may be omitted
reviewRatingNoRating range from 0 to 5: {min, max}; either bound may be omitted
convToCartPdpNoCart conversion-rate range: {min, max}; either bound may be omitted
page.pageSizeNoItems per page, default 20
monthlyRevenueNoMonthly revenue range in RUB: {min, max}; either bound may be omitted
variationsMergeNoWhether to merge variants: 0 do not merge, 1 merge
monthlySalesRateNoSales growth-rate range: {min, max}; either bound may be omitted
questionsAndAnswersNoQuestion-and-answer count range: {min, max}; either bound may be omitted
returnCancellationRateNoReturn and cancellation-rate range: {min, max}; either bound may be omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds return-field visibility (SKU, price in RUB, lost revenue, conversion, listing days/months), which is genuinely useful, but says nothing about pagination caps, rate limits, or data freshness of the underlying dataset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences are dense and useful, but the long 'Trigger when the user mentions ...' list repeats the tool name a dozen times as keyword stuffing and adds no decision-relevant information. The definition would be stronger and shorter without it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 31-parameter nested-filter tool with no output schema, the description does cover both the filter dimensions and the shape of the returned report, which is the main thing the schema cannot convey. It still omits guidance on required pagination object semantics, result limits, and how this differs from the sibling Ozon product search tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the 31 parameters is already documented including ranges, enums, and the searchDate month convention. The description only restates the same filter vocabulary at a higher level and adds no syntax or defaulting guidance beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (filter Ozon products by multi-dimensional metrics, return product-level report fields) and enumerates the filter dimensions and return fields concretely. However it never distinguishes itself from close siblings such as nexscope_ozon_product_search or nexscope_ozon_product_detail_search, so an agent cannot tell which one to open without reading both schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage contexts (product selection, competitor analysis, best-seller mining, price/conversion band filtering) plus trigger phrases. It gives no exclusions and names no alternatives, so the when-not-to-use case is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.