---
title: "corestack_orders_list"
url: https://docs.corefinity.com/mcp/tools/corestack_orders_list
type: tool
last_updated: 2026-11-13
feature: order
related:
  - https://docs.corefinity.com/api/reference/billing/list-orders.md
  - https://docs.corefinity.com/guides/billing/orders.md
---
# corestack_orders_list

**Orders.** Page through the company's orders (new sites and clusters bought), newest first, with each state's count. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Page through the company's orders (new sites and clusters bought), newest first, with each state's count. The same list as Company › Orders in the Control Panel and `GET /api/corestack/orders`.

## Inputs

- `state` (one of `all`, `open`, `completed`, `failed`, `ended`, default `all`)
- `kind` (one of `site`, `cluster`)
- `user_id` (integer, at least 1): Who placed it (an id from placers).
- `search` (string, at most 100 characters): An order number, a domain or a cluster name.
- `cursor` (string, matching `^\d{1,18}$`): next_cursor from the previous page.

`kind`, `user_id` and `search` narrow the rows and every state's count alike. `total` counts all of the person's orders whatever the filters; `placers` lists who placed them. Links (`status_href`, `continue_href`, `restart_href`, `start_href`) open in the Control Panel.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cursor": {
      "description": "next_cursor from the previous page.",
      "pattern": "^\\d{1,18}$",
      "type": "string"
    },
    "kind": {
      "enum": [
        "site",
        "cluster"
      ],
      "type": "string"
    },
    "search": {
      "description": "An order number, a domain or a cluster name.",
      "maxLength": 100,
      "type": "string"
    },
    "state": {
      "default": "all",
      "enum": [
        "all",
        "open",
        "completed",
        "failed",
        "ended"
      ],
      "type": "string"
    },
    "user_id": {
      "description": "Who placed it (an id from placers).",
      "minimum": 1,
      "type": "integer"
    }
  },
  "type": "object"
}
```

## Refusals

- `orders_forbidden`: only the company's owner or someone with a billing role can see its orders (the Control Panel's words).
- `pin_refused`: the token is limited to some sites; the orders name every site and cluster the company bought, so it needs the step-up to the whole company.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_orders_list",
  "arguments": {
    "state": "open"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_orders_list with state open. (Orders.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/orders](https://docs.corefinity.com/api/reference/billing/list-orders.md)
- Guide: [Orders](https://docs.corefinity.com/guides/billing/orders.md)
