io.github.dontsovcmc/ozon-seller
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OZON_API_KEY | Yes | Api-Key from Ozon Seller API keys | |
| OZON_TIMEOUT | No | HTTP request timeout in seconds | 30 |
| OZON_CLIENT_ID | Yes | Client-Id from Ozon Seller API keys | |
| OZON_FILE_TIMEOUT | No | File download timeout in seconds | 60 |
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_searchA | Find available Ozon Seller API actions by intent. Args: query: natural language description of what you want to do domain: optional filter (products, fbs, fbo, categories, finance, analytics, warehouses, returns, chats, promos, strategies, rating, reports, reviews, questions, cancellations, certificates, barcodes, brands) limit: max results (default 10) |
| ozon_executeA | Execute an Ozon Seller API action by ID. Use ozon_search first to find the action ID and its parameter schema. Args: action: action ID from ozon_search results (e.g. "product-list") params_json: JSON object with action parameters matching the schema |
| ozon_execute_fileC | Execute an Ozon Seller API action that downloads a file. Args: action: action ID for download actions file_path: local file path to save the downloaded file params_json: JSON object with action parameters |
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 3 tools
Each tool has a distinct purpose: ozon_search discovers actions, ozon_execute executes general API calls, and ozon_execute_file handles file downloads. No overlap in core functionality.
All tools follow the consistent pattern of 'ozon_' prefix with a verb_noun structure (search, execute, execute_file). No mixing of conventions.
Only 3 tools, but they are designed as a meta-interface to a large API. The minimal set is appropriate for the gateway pattern, though it may feel thin for complex workflows.
The meta-approach covers the entire Ozon Seller API via search and execute, with a dedicated tool for file downloads. Minor gap: no direct tools for common operations, but the discovery mechanism mitigates this.