Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_my_trades

Read-onlyIdempotent

Retrieve your executed spot trades (fills) for a single trading pair, with optional filtering by order, time range, or trade ID. See exact price, quantity, fees, and your buy/sell side.

Instructions

Fetch YOUR executed trades (fills) for one symbol.

Calls GET /api/v3/myTrades (signed; IP weight 20, or 5 when order_id is given). symbol is mandatory — Binance has no endpoint that returns trades across every symbol, which is what binance_get_all_my_trades exists to work around.

Unlike the public trade endpoints, isBuyer here is your own side of the fill (public trades expose isBuyerMaker, the aggressor's side, instead).

When to Use:

  • To see the fills of one pair, or of one order (order_id).

  • To check the exact price, fee and fee asset of a known trade.

When NOT to Use:

  • For the whole account's history — use binance_get_all_my_trades.

  • For orders that never filled — use binance_get_all_orders (spot_orders).

  • For anonymous market trades — use binance_get_recent_trades (market_data).

Returns: Markdown: a table of up to 100 fills (time, side, price, qty, quote qty, commission, maker/taker) plus totals for the page — bought/sold base and quote, and fees broken down by fee asset. JSON: the full page plus the same totals.

Pagination / Windows: Binance accepts only these combinations: symbol; symbol+order_id; symbol+from_id; symbol+start_time; symbol+end_time; symbol+start_time+end_time; symbol+order_id+from_id. start_time and end_time are each legal on their own — only together do they have to span at most 24 hours, and a wider window is rejected here with no call spent. To page, re-call with from_id = the last id + 1.

Examples: params = {"symbol": "BTCUSDT", "limit": 100} params = {"symbol": "BTCUSDT", "order_id": 987654321} params = {"symbol": "ETHUSDT", "start_time": "2024-01-01T00:00:00Z", "end_time": "2024-01-01T23:59:59Z"} params = {"symbol": "ETHUSDT", "from_id": 4211999}

Error Handling: An over-wide window or an illegal combination is refused locally with an Error: … string and no API call. -2015 means the key lacks Reading or the IP is not allowlisted; -1121 means the symbol does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds significant behavioral context: the signed endpoint and IP weight, the isBuyer side semantics, local rejection of invalid windows, pagination via from_id, and error code meanings. This far exceeds what annotations alone convey.

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 every section earns its place: use cases, exclusions, return format, pagination rules, examples, and error handling. Clear headings and front-loaded purpose make it scannable and practical for an agent.

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?

Given the complexity of the endpoint, the description is complete: it covers mandatory parameters, valid combinations, limits, output formats, pagination strategy, and error handling. An agent has everything needed to invoke this tool correctly and interpret results.

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?

Although the measured schema coverage is 0%, the description thoroughly compensates by explaining every relevant parameter, legal combinations, the 24-hour window restriction, and providing four concrete usage examples. It adds meaning far beyond the raw schema properties.

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 opens with a specific verb and resource: 'Fetch YOUR executed trades (fills) for one symbol.' It clearly distinguishes the tool from public trade endpoints and from the sibling binance_get_all_my_trades, making the tool's scope unmistakable.

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?

There are explicit 'When to Use' and 'When NOT to Use' sections that name alternatives like binance_get_all_my_trades, binance_get_all_orders, and binance_get_recent_trades. This gives the agent exact routing conditions and exclusions.

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

Deploy Server

Other Tools