Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

get_order_history

Read-only

Retrieve your order history from Bybit by specifying product type. Filter by symbol, order ID, status, and more, with pagination support.

Instructions

Query order history.

    Args:
        category: Product type - spot, linear, inverse, option
        symbol: Symbol name
        orderId: Order ID
        orderLinkId: User custom order ID
        orderStatus: Order status - New, PartiallyFilled, Filled, Cancelled, etc.
        limit: Limit per page (max 50, default 20)
        cursor: Pagination cursor
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
symbolNo
orderIdNo
categoryYes
orderLinkIdNo
orderStatusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds parameter details but does not disclose pagination behavior, response size limits, or concurrency implications. With annotations, the bar is lower, so a 3 is appropriate.

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

Conciseness4/5

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

The description is a concise docstring list, front-loaded with the purpose. Every sentence adds value. Could be slightly more efficient but no fluff.

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?

Given 7 parameters, 1 required, and an output schema (which means return values need not be described), the description is adequately detailed. It covers all parameters and their roles. Missing mention of default behavior or error handling, but that is not critical.

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

Parameters4/5

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

Schema description coverage is 0%, but the description explains all 7 parameters with examples (e.g., category: 'spot, linear, inverse, option', orderStatus: 'New, PartiallyFilled, Filled, Cancelled, etc.'). This adds significant meaning beyond the bare schema. However, limit and cursor explanations are minimal ('Pagination cursor').

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

Purpose5/5

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

The description clearly states 'Query order history' which is a specific verb-resource pair. This distinguishes it from sibling tools like 'get_open_orders' (current open orders) and 'get_trade_history' (executed trades).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. With many sibling tools like get_open_orders, get_trade_history, get_closed_pnl, the description does not differentiate use cases or provide when-not-to-use hints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/workspace/bybit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server