OZON MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ozon_list_sectionsA | List all Ozon API sections (Seller + Performance) with method counts. Use this first to orient yourself in the API. Returns sections grouped by api ('seller' or 'performance'), each with the human-readable section name, the underlying tag, and the number of methods inside. |
| ozon_search_methodsA | Full-text search across all Ozon API methods. Searches over operation_id, path, summary, description, section, and tag using BM25 ranking with field boosting (summary x4, path/op_id x3, description x1). Supports Russian and English queries with stemming. Args: query: free-text query, e.g. "list of postings" or "финансовые транзакции" section: optional filter — match by section name or tag (case-insensitive substring) api: optional filter — "seller" or "performance" safety: optional filter — "read", "write", or "destructive" limit: max results to return (default 10) |
| ozon_describe_methodA | Get a complete description of one Ozon API method. Returns the method's metadata plus fully-resolved JSON Schema for request and responses. All $ref pointers are inlined; oneOf/anyOf/allOf combinators are preserved verbatim. When knowledge layer is loaded, also includes rate_limit, quirks, examples, and related methods — everything an agent needs to call the method correctly. Provide either |
| ozon_get_sectionA | List all methods inside a section (by section name or tag). Args: query: section name or tag, e.g. "FinanceAPI", "Финансовые отчёты", "ProductAPI" |
| ozon_get_related_methodsA | Find methods related to a given one (auto-extracted from doc links + workflows). Returns methods that this operation links to in its description, plus methods that link back to it. Useful for understanding which calls you'll likely need together when integrating a feature. Args: operation_id: source method max_hops: 1 = direct neighbours, 2 = neighbours of neighbours |
| ozon_list_workflowsA | List all curated workflows, optionally filtered by category. Workflows are step-by-step recipes for chaining Ozon API methods into
real data pipelines or analytical reports. Use Args:
category: optional filter — one of "catalog", "orders",
"analytics", "health", "pricing", "content", "advertising",
"warehouse", "returns", "finance". When provided, only
workflows in that category are returned. |
| ozon_get_workflowA | Get the full step-by-step plan for one workflow. Returns ordered steps with operation_ids, pagination/batching/concurrency
guidance, recommended DB schema, and known gotchas. Analytical
workflows additionally carry Args: name: workflow name from ozon_list_workflows, e.g. "sync_orders_fbs" or "oos_risk_analysis" |
| ozon_get_rate_limitsA | Look up rate limits for a method, section, or the whole API. Without arguments returns all known limits. With operation_id, returns the most specific limit (per-method overrides per-section overrides global). NOTE: Many limits in v0.2 are conservative guesses (source: 'guess'). Verify against real Ozon responses before relying on them in production. |
| ozon_get_error_catalogA | Look up Ozon API errors and their solutions. Without arguments returns all known errors. With code (e.g. "429" or "InvalidArgument") filters by code. With operation_id returns errors specific to that method plus all generic ones. |
| ozon_get_examplesB | Get hand-crafted request examples for one method. Examples are real, validated payloads matching the method's request schema — copy them as starting points for your own calls. |
| ozon_get_swagger_metaA | Return metadata about the bundled Ozon swagger snapshots. Tells the caller which spec version we are shipping, how many methods it contains, when the snapshot was refreshed, and the SHA-256 of the file. Useful for:
Returns |
| ozon_list_methods_for_subscriptionA | List all Ozon methods that mention a specific subscription tier. Useful when an agent wants to know "what extra capabilities do I unlock by upgrading to Premium Plus?" or "which methods will fail without Premium?". Tiers are auto-extracted from method documentation, so this is a hint, not a contract — the actual hard 403 set may differ. Args: tier: one of UNSPECIFIED, PREMIUM_LITE, PREMIUM, PREMIUM_PLUS, PREMIUM_PRO |
| ozon_search_operations_knowledgeA | 搜索中文Ozon运营知识库。 适用于经营模式、跟卖、精铺、选品、商品卡、定价、仓库、物流、货代、 促销、广告、履约、售后和风险问题。先搜索获取相关片段ID,再使用 ozon_get_operations_knowledge 读取完整证据。 Args: query: 搜索关键词(中文),例如"跟卖怎么选品""精铺差异化""货代发货流程" limit: 返回结果数量(默认5,最大10) module: 可选,按模块筛选 lesson_id: 可选,按课程ID筛选 verification_required: 可选,筛选需要时效复核的片段 |
| ozon_get_operations_knowledgeA | 根据chunk_id读取一个完整的Ozon运营知识片段。 应在 ozon_search_operations_knowledge 返回相关chunk_id后调用, 用于取得完整证据并组织客户答案。 Args: chunk_id: 知识片段ID,来自搜索结果的chunk_id字段 |
| ozon_list_operations_topicsA | 列出中文Ozon运营知识库的课程目录和主题。 可按模块、课程标题或关键词筛选,用于了解知识库覆盖范围。 Args: query: 可选,按课程标题或关键词筛选 module: 可选,按模块筛选 limit: 返回数量(默认20) offset: 分页偏移(默认0) include_chunk_ids: 是否返回chunk_id列表(默认false,避免上下文过大) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool has a clear, distinct purpose: searching methods, describing a method, listing sections, retrieving workflows, rate limits, errors, examples, and separate Chinese knowledge base tools. No two tools overlap in functionality.
Most tools follow the 'ozon_verb_noun' pattern (e.g., search_methods, get_workflow), but a few are inconsistent: 'ozon_get_section' actually lists methods rather than retrieving a section, and 'describe_method' vs 'get_section' uses different verbs for similar retrieval actions. Overall still predictable.
15 tools is reasonable for an API exploration and knowledge base server. It covers a comprehensive set of actions without being excessive or sparse.
The server covers all major aspects of Ozon API exploration: sections, methods, workflows, limits, errors, examples, metadata, subscription details, and a Chinese operations knowledge base. No obvious missing functionality for its stated purpose.