# get_board_item (/docs/build/mcp-reference/get_board_item)

{/* GENERATED by scripts/generate-mcp-reference.mjs from the MCP server tools/list. Do not edit. */}

| Group | Access | MCP name |
| --- | --- | --- |
| Boards (beta) | Read-only | `get_board_item` |

## Description [#description]

The description the MCP server sends to the model, word for word. Its rules apply to every call.

> One item from a board in full, by its ref from get_board (like b3): all of its text, the user's note, its numbers and link, and for an image what it shows. Over MCP, always pass board: its id or title from list_boards.

## Arguments [#arguments]

| Argument | Type | Required | Description |
| --- | --- | --- | --- |
| `board` | `string` | No | Board id or title. In a Coach chat about a board, omit it to use that board. Max length 200. |
| `ref` | `string` | Yes | The item's ref from get_board, like b3. Min length 1. Max length 40. |

## Example call [#example-call]

The smallest valid request: required arguments only, with placeholder values.

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_board_item",
    "arguments": {
      "ref": "…"
    }
  }
}
```

## Annotations [#annotations]

| Hint | Value |
| --- | --- |
| `readOnlyHint` | `true` |
| `destructiveHint` | `false` |
| `openWorldHint` | `false` |

The full input and output JSON Schemas for every tool are in [/mcp-tools.json](/mcp-tools.json).
