> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List members

> List this workspace's members with their role and, when narrowed, the exact projects they can see.

`list_members`

List this workspace's members with their role and, when narrowed, the exact projects they can see. A null project list means every project.

<Note>Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL\_API\_URL; production does not expose these command routes.</Note>

| Access          | Behavior         |
| --------------- | ---------------- |
| `projects:read` | Reads saved data |

Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list_members",
      "arguments": {}
    }
  }
  ```

  ```bash CLI theme={null}
  linktrail call list_members --args '{}'
  ```

  ```bash HTTP theme={null}
  curl "$LINKTRAIL_API_URL/v1/commands/list_members" \
    -H "Authorization: Bearer $LINKTRAIL_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{}'
  ```
</CodeGroup>

## Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in `structuredContent` and in a text content block; generic HTTP and CLI return the JSON result directly.

```json theme={null}
{
  "items": [
    {
      "user_id": "user_example",
      "role": "owner",
      "project_ids": null,
      "created_at": "2026-09-13T12:00:00.000Z"
    }
  ]
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

This operation accepts an empty object.

### Validation and omitted values

A null project grant means workspace-wide access. Member limits remain the ceiling for existing credentials.

## Output fields

Fields inside optional or nullable parents apply only when that parent exists. [Common schema conventions](/reference/schemas) explain evidence states, empty lists and extensions.

| Field                  | Type         | Presence | Meaning and constraints                                                       |
| ---------------------- | ------------ | -------- | ----------------------------------------------------------------------------- |
| `items`                | array        | Required | Records in this bounded page.                                                 |
| `items[].workspace_id` | string       | Optional | Workspace that owns this record.                                              |
| `items[].user_id`      | string       | Required | user id recorded for this result.                                             |
| `items[].role`         | string       | Required | role recorded for this result.                                                |
| `items[].project_ids`  | array / null | Optional | Accessible project identifiers; null grants access to all workspace projects. |
| `items[].created_at`   | string       | Optional | UTC timestamp when the record was created.                                    |

[Download input schema](/schemas/list_members.input.json) · [Download output schema](/schemas/list_members.output.json)

## Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict.

See [error recovery](/reference/errors) for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

## HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See [HTTP route details](/reference/http/routes).

| Method and route  | Success | Details                                          |
| ----------------- | ------- | ------------------------------------------------ |
| `GET /v1/members` | 200     | Remaining read arguments go in query parameters. |

## Continue

[get\_workspace](/reference/commands/get_workspace)

Follow the [related workflow](/guides/connect-http), inspect [capability status](/capability-status), or return to the [command index](/reference/index).