Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

Ozon Seller Products

nexscope_ozon_seller_products
Read-only

Nexscope Ozon Russia seller drill-down product list by seller ID. Returns all SKUs under a seller with complete metrics: sales, revenue, price, rating, stock, turnover, lost revenue, supporting multi-dimensional numeric filters, sorting, and currency conversion. Use for store structure analysis, seller bestseller analysis, competitor store benchmarking. Trigger when the user mentions Ozon seller products, Ozon store analysis, Ozon seller drill-down, Ozon seller SKUs, Ozon store bestsellers, Ozon competitor store, Nexscope seller, Ozon seller drill-down, Ozon shop audit, Russian marketplace seller SKUs, Ozon store structure. Also trigger when the intent is to view all products and their sales performance under an Ozon seller ID, even without explicitly mentioning Nexscope.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1
endDateNoStatistics end date YYYY-MM-DD; latest is yesterday
filtersNoNumeric conditions combined with AND
currencyNoCurrency code, default RUB, e.g., USD
pageSizeNoRows per page 1-100, default 100
sellerIdYesOzon seller ID (numeric string), matching the seller identifier in product lists/seller rankings
sortFieldNoSort column name (snake_case), e.g., sales, revenue, final_price, balance, rating
startDateNoStatistics start date YYYY-MM-DD; latest is yesterday
includeFbsNoWhether to include FBS data
currencyRateNoCustom exchange rate (for non-default currency)
sortDirectionNoasc / desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / filters / items
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "field": {
+      "description": "Snake-case numeric column name, such as sales, final_price, rating, comments, balance, revenue, days_in_stock, turnover_days, lost_profit or category_position",
+      "example": "sales",
+      "type": "string"
+    },
+    "op": {
+      "description": "GTE, LTE, GT, LT, EQ, NOT_EQ or BETWEEN",
+      "example": "GTE",
+      "type": "string"
+    },
+    "value": {
+      "description": "Primary value; lower bound for BETWEEN",
+      "example": 1,
+      "type": "number"
+    },
+    "value2": {
+      "description": "Required upper bound for BETWEEN",
+      "example": 2,
+      "type": "number"
+    }
+  },
+  "required": [],
+  "type": "object"
+}
    • removedInput schema / properties / filters[].field
      Removed value: -{
-  "description": "Snake-case numeric column name, such as sales, final_price, rating, comments, balance, revenue, days_in_stock, turnover_days, lost_profit or category_position",
-  "example": "sales",
-  "type": "string"
-}
    • removedInput schema / properties / filters[].op
      Removed value: -{
-  "description": "GTE, LTE, GT, LT, EQ, NOT_EQ or BETWEEN",
-  "example": "GTE",
-  "type": "string"
-}
    • removedInput schema / properties / filters[].value
      Removed value: -{
-  "description": "Primary value; lower bound for BETWEEN",
-  "example": 1,
-  "type": "number"
-}
    • removedInput schema / properties / filters[].value2
      Removed value: -{
-  "description": "Required upper bound for BETWEEN",
-  "example": 2,
-  "type": "number"
-}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results carry complete metrics and support filters, sorting and currency conversion, but says nothing about pagination limits, data freshness beyond the schema's date notes, or response shape. Adequate but not rich.

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 sentence is well front-loaded, but the trigger section is a bloated keyword dump that repeats 'Ozon seller drill-down' twice and pads with redundant variants. Roughly half the text is trigger stuffing rather than information an agent needs to invoke the tool correctly.

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

Completeness4/5

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

For an 11-parameter read-only listing tool with no output schema, the description covers what is returned (SKUs plus sales, revenue, price, rating, stock, turnover, lost revenue) and that filtering, sorting and currency conversion are supported. The remaining gap — pagination behavior and result limits — is minor given the fully documented schema.

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 parameter including the filters object, sortField, currencyRate and includeFbs is already documented in the schema. The description only gestures at 'multi-dimensional numeric filters, sorting, and currency conversion' without adding syntax, defaults or field-name guidance. Baseline 3 is correct when the schema does the heavy lifting.

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?

The first sentence names a specific verb and resource ('drill-down product list by seller ID') and enumerates the returned metrics, which clearly separates it from generic search tools. It never names a sibling such as nexscope_ozon_brand_products or nexscope_ozon_product_search to state what it is not, so it falls short of a 5.

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?

It gives concrete use cases (store structure analysis, bestseller analysis, competitor store benchmarking) and lists trigger phrasings, so an agent knows when to reach for it. It stops short of exclusions or alternatives — for example, when to prefer brand-level or category-level Ozon tools instead of a seller drill-down.

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

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources