Jupiter Get Limit Orders
jupiter_getLimitOrdersRetrieve active or historical limit orders for a given wallet address. Filter by token mint or order status to manage Jupiter protocol orders.
Instructions
Get all limit orders (active and optionally historical) for a wallet. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"wallet": "<wallet>",
"orderStatus": "<orderStatus>"
},
"name": "jupiter_getLimitOrders"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page pagination control for Jupiter Get Limit Orders. | |
| limit | No | Limit controlling the maximum number of results returned by Jupiter Get Limit Orders. | |
| wallet | Yes | Wallet address to query | |
| inputMint | No | Token mint address (base58) | |
| outputMint | No | Token mint address (base58) | |
| orderStatus | Yes | Filter by order status: "active" for open orders, "history" for filled/cancelled |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | MCP content blocks returned to the caller. | |
| isError | No | True when the tool result represents an application-level error. |