amazing-binance-mcp

Overview Schema Source Related Servers Discussions Admin

binance_get_all_order_lists

Read-onlyIdempotent

Retrieve account-wide order lists — working, completed, and cancelled — across all symbols with optional from_id cursor or 24-hour time window for history reconstruction.

Instructions

List this account's order lists — working, completed and cancelled — across symbols.

Calls GET /api/v3/allOrderList (SIGNED, IP weight 20). There is no symbol filter: the endpoint is account-wide. Narrow it with from_id (lists with orderListId >= it) or a start_time/end_time window — Binance forbids combining them, and that is rejected locally. The window may not exceed 24 hours, also checked here so you get a clear message instead of Binance's -1127.

When to Use:

Reconstructing which brackets existed during a given day.
Paging list history forward with a from_id cursor.

When NOT to Use:

For what is armed right now — binance_get_open_order_lists costs weight 6.
For one known list — binance_get_order_list costs weight 4.
For plain (non-list) orders — binance_get_all_orders (spot_orders.py).

Returns: A markdown table (time, symbol, orderListId, contingencyType, listStatusType, listOrderStatus, listClientOrderId, leg count) capped at 50 rows, or the raw array with response_format="json".

Pagination: limit is 1-1000 (Binance default 500) and at most 50 rows are rendered; use response_format="json" or narrow the window for the rest. from_id pages forward: pass the last orderListId you saw, plus one.

Windows: start_time/end_time accept epoch ms or ISO-8601 and must span 24 h or less together. Omit everything to get the most recent limit lists.

Examples: params = {"limit": 10} params = {"start_time": "2026-09-22T00:00:00Z", "end_time": "2026-09-22T23:59:59Z"} params = {"from_id": 27}

Error Handling: A window wider than 24 h, and from_id combined with a time bound, are both rejected locally. -1127 from Binance means a too-wide window reached it anyway; -1128 is an invalid parameter combination. -2015 means the key lacks permission or this IP is not allowlisted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds substantial behavior: SIGNED endpoint, IP weight, no symbol filtering, local rejection of invalid parameter combinations, 24-hour window limit, error codes (-1127, -1128, -2015), and response rendering caps. This goes well beyond the annotations and structured fields.

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

Conciseness5/5

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

The description is long but highly structured with clear sections (When to Use, When NOT to Use, Returns, Pagination, Windows, Examples, Error Handling). The core purpose is front-loaded, and every sentence adds operational value. No filler or tautology.

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

Completeness5/5

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

For a read-only historical listing tool with an output schema, the description is complete: it explains the return shape (markdown table with specific fields or raw JSON), the pagination model, local validation, error semantics, and the exact endpoint. An agent has everything needed to select and invoke this tool correctly.

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

Parameters5/5

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

Even though the schema includes per-property descriptions, the tool description adds crucial semantics: how `from_id` pages forward ('pass the last orderListId you saw, plus one'), accepted time formats (epoch ms or ISO-8601), the 24-hour window restriction, the mutual exclusivity of `from_id` with time bounds, and the interpretation of `limit` vs. the 50-row rendering cap. Concrete examples further clarify parameter usage.

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 opening line states a specific verb ('List'), a resource ('order lists'), a scope ('this account', 'account-wide', 'across symbols'), and includes all statuses ('working, completed and cancelled'). It also names the exact endpoint and differentiates itself from sibling tools like binance_get_open_order_lists and binance_get_all_orders.

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

Usage Guidelines5/5

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

The 'When to Use' and 'When NOT to Use' sections are explicit, naming alternative tools (binance_get_open_order_lists, binance_get_order_list, binance_get_all_orders) and the conditions that select each. No inference is required from the agent.

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

Deploy Server