> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/mcp/tools/usage-sharing-and-comments.md).

# Usage, sharing and comment tools

Reference for the FLORA MCP tools that read balance and spend in US dollars, share projects by link, and manage comment threads.

These [FLORA MCP](https://flora.ai/mcp) tools check what a workspace can spend, share a project by link, and work with its comment threads. [`flora_get_usage`](#flora_get_usage) reports balance and spend in US dollars, the unit the agent shows the user. Sharing and comments are visible to other people, so the agent should change them only when the user asks.

For how agents price work and handle a low balance, see [FLORA MCP cost, balance and limits](https://docs.flora.ai/mcp/cost-and-limits.md).

{% hint style="warning" %}
**Cost rule.** Price first: call `flora_create_generations` with `quote: true` and show the user the cost in US dollars. Run the same request without `quote` only after they approve. On `insufficient_credits` or any `BILLING_*` error, stop and pass the message on. Don't retry. Check balance and spend with `flora_get_usage`. A failed run isn't charged; a retry is a new run and is billed again.
{% endhint %}

| Tool                                                              | What it does                                                                                                      | Labels              |
| ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------- |
| [`flora_get_usage`](#flora_get_usage)                             | Read a workspace's balance and spend, or an organization's spend, in US dollars.                                  | read-only           |
| [`flora_share_project`](#flora_share_project)                     | Share a project by link with view or edit access, the way the canvas Share tab does, and return the link.         | writes, destructive |
| [`flora_get_project_sharing`](#flora_get_project_sharing)         | Read how a project is shared: link mode, the active link, owner and members.                                      | read-only           |
| [`flora_update_project_sharing`](#flora_update_project_sharing)   | Change a project's link sharing: unshare it, limit it to view, open it for editing, or set or clear a passphrase. | writes, destructive |
| [`flora_list_comment_threads`](#flora_list_comment_threads)       | List a project's comment threads, newest first, with each thread's status, pin position and a preview.            | read-only           |
| [`flora_get_comment_thread`](#flora_get_comment_thread)           | Read one comment thread with its live messages, oldest first.                                                     | read-only           |
| [`flora_create_comment_thread`](#flora_create_comment_thread)     | Pin a new comment thread on a project canvas and post its first comment. Collaborators see it on the canvas.      | writes              |
| [`flora_reply_to_comment_thread`](#flora_reply_to_comment_thread) | Post a reply on an open comment thread.                                                                           | writes              |
| [`flora_resolve_comment_thread`](#flora_resolve_comment_thread)   | Mark a comment thread resolved. Its comments are kept.                                                            | writes              |
| [`flora_reopen_comment_thread`](#flora_reopen_comment_thread)     | Reopen a resolved comment thread so it accepts replies again.                                                     | writes              |
| [`flora_delete_comment`](#flora_delete_comment)                   | Permanently delete one comment from a thread.                                                                     | writes, destructive |

## flora\_get\_usage <a href="#flora_get_usage" id="flora_get_usage"></a>

Read a workspace's balance and spend, or an organization's spend, in US dollars.

**Labels:** read-only

**Shown in clients as:** Get usage

**Use when:** The user asks what they can still spend or what they've spent, or before a big batch.

**Don't use when:** You want the price of a specific request: quote it with [`flora_create_generations`](https://docs.flora.ai/mcp/tools/generations.md#flora_create_generations) and `quote: true`. Never add balances across workspaces, because workspaces in one organization may share a pool.

**Arguments**

| Argument          | Type   | Required | Notes                                                                                                                                                                                       |
| ----------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `workspace_id`    | string | no       | Workspace to read (ws\_…), from flora\_list\_workspaces. Pass this or organization\_id, not both.                                                                                           |
| `organization_id` | string | no       | Organization to read spend across (org\_…): the organization\_id flora\_list\_workspaces returns for a workspace. Pass this or workspace\_id, not both.                                     |
| `start_date`      | string | no       | First UTC day to include, as YYYY-MM-DD. Defaults to 29 days before end\_date.                                                                                                              |
| `end_date`        | string | no       | Last UTC day to include, as YYYY-MM-DD. Defaults to today (UTC); a workspace read refuses a later day.                                                                                      |
| `group_by`        | string | no       | With organization\_id only, adds one breakdown: workspace (by\_workspace), model (by\_model plus unattributed\_cost) or day (by\_day). Omit for totals. One of `workspace`, `model`, `day`. |

**Returns:** For a workspace: `available_cost` (what can be spent now) and `balance_scope` (`workspace` or `caller`), plus spend (`total_cost`, `classified_runs`, `runs_by_category`) when the caller may see it. For an organization: spend only, with `by_workspace`, `by_model` or `by_day` when you pass `group_by`. When spend is unavailable, relay the reason (`entitlement_missing` or `permission_missing`); it never means zero spend.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_workspaces`](https://docs.flora.ai/mcp/tools/workspaces-and-projects.md#flora_list_workspaces)

**Usually comes before:** [`flora_create_generations`](https://docs.flora.ai/mcp/tools/generations.md#flora_create_generations)

**Example prompt:** "How much can I still spend in my FLORA workspace?"

**Example call:**

```json
{
  "workspace_id": "ws_123"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Read balance and spend in USD, not credits, for one workspace (workspace_id, ws_…) or across an organization (organization_id, org_…); pass exactly one. Unsure which workspace? Call flora_list_workspaces first: it returns both ids, and current_workspace_id when the user is already in one. Workspace: available_cost is what can be spent now. It is current rather than limited to the date range, does not reflect workspace spending caps, and does not guarantee a run will be admitted. What it covers depends on the caller, who may see only their own balance, and workspaces of one organization may share a pool, so never sum it across workspaces. balance_scope workspace (billing permission on a plan with usage reporting): the pool's balance, and spend carries the workspace's total_cost, classified_runs and runs_by_category for the range. balance_scope caller (anyone else, including billing admins on a plan without usage reporting): only the caller's own allowance, plus member_limit when a spending limit binds them, and spend is unavailable with reason entitlement_missing (the plan lacks usage reporting) or permission_missing (the caller lacks billing permission). Relay that reason; it never means zero spend. summary_unavailable means the totals could not be computed; a shorter range may help. classified_runs counts only runs with a known output type; unclassified spend still counts in total_cost. Organization: spend only, no balance. It returns total_cost, total_runs and runs_by_category across all its workspaces, and group_by adds by_workspace, by_model or by_day. It needs billing permission in an organization with multiple workspaces enabled. Dates are inclusive UTC days (YYYY-MM-DD) and default to the 30 days ending today; a workspace range spans at most 31 days and ends no later than today, an organization range at most 366 days. An API key needs billing permission on the workspace; other workspaces and organizations return 403.
```

{% endcode %}

</details>

## flora\_share\_project <a href="#flora_share_project" id="flora_share_project"></a>

Share a project by link with view or edit access, the way the canvas Share tab does, and return the link.

**Labels:** writes · destructive

**Shown in clients as:** Share project

**Use when:** The user asks for a share link.

**Don't use when:** You only want to see the current sharing ([`flora_get_project_sharing`](#flora_get_project_sharing)) or to unshare ([`flora_update_project_sharing`](#flora_update_project_sharing) with `sharing_mode: "restricted"`). Give the link to the user; don't post it anywhere else.

**Arguments**

| Argument         | Type    | Required | Notes                                                                                                                                                                   |
| ---------------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id`     | string  | yes      | Project to share (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `access`         | string  | yes      | What the link grants: view or edit. One of `view`, `edit`.                                                                                                              |
| `allow_comments` | boolean | no       | Whether visitors arriving through the link may comment (default on).                                                                                                    |
| `passphrase`     | string  | no       | Require this passphrase before the link resolves.                                                                                                                       |

**Returns:** The share link. Anyone with it gets its access. `access: "edit"` may be refused with `paid_plan_required`, and `access: "view"` never downgrades a project already shared for editing.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_get_project_sharing`](#flora_get_project_sharing)

**Example prompt:** "Give me a view-only link to my Spring campaign project."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "access": "view",
  "allow_comments": true
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Share a project by link, the way the canvas Share tab does, and return the link. Anyone who has the link gets its access, so hand it to the user rather than posting it elsewhere. `access: "edit"` may be refused on the workspace plan (paid_plan_required); `access: "view"` never downgrades a project already shared for editing (its view link is returned). A passphrase given here lands in the chat transcript.
```

{% endcode %}

</details>

## flora\_get\_project\_sharing <a href="#flora_get_project_sharing" id="flora_get_project_sharing"></a>

Read how a project is shared: link mode, the active link, owner and members.

**Labels:** read-only

**Shown in clients as:** Get project sharing

**Use when:** The user asks who can see a project or whether it's shared.

**Don't use when:** You want to change sharing: use [`flora_share_project`](#flora_share_project) or [`flora_update_project_sharing`](#flora_update_project_sharing).

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                  |
| ------------ | ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id` | string | yes      | Project to read (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |

**Returns:** The link sharing mode, the active share link (only when the user may manage sharing), the owner and the members.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_projects`](https://docs.flora.ai/mcp/tools/workspaces-and-projects.md#flora_list_projects)

**Usually comes before:** [`flora_share_project`](#flora_share_project), [`flora_update_project_sharing`](#flora_update_project_sharing)

**Example prompt:** "Who has access to my Spring campaign project?"

**Example call:**

```json
{
  "project_id": "prj_abc"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Read how a project is shared: link sharing mode, the active share link (only when the user may manage sharing), owner, and members.
```

{% endcode %}

</details>

## flora\_update\_project\_sharing <a href="#flora_update_project_sharing" id="flora_update_project_sharing"></a>

Change a project's link sharing: unshare it, limit it to view, open it for editing, or set or clear a passphrase.

**Labels:** writes · destructive

**Shown in clients as:** Update project sharing

**Use when:** The user asks to unshare a project, revoke an edit link, or change link comments or the passphrase.

**Don't use when:** The user just wants a link: use [`flora_share_project`](#flora_share_project). `sharing_mode: "restricted"` stops every existing link working, so confirm with the user first.

**Arguments**

| Argument              | Type           | Required | Notes                                                                                                                                                                    |
| --------------------- | -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id`          | string         | yes      | Project to change (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `sharing_mode`        | string         | no       | restricted (unshare), view, or edit. One of `restricted`, `view`, `edit`.                                                                                                |
| `allow_link_comments` | boolean        | no       | Whether visitors arriving through the link may comment.                                                                                                                  |
| `passphrase`          | string or null | no       | A string sets the passphrase; null clears it.                                                                                                                            |

**Returns:** The project's updated sharing. Only the fields you pass change; `edit` may be refused with `paid_plan_required`.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_get_project_sharing`](#flora_get_project_sharing)

**Example prompt:** "Unshare my Spring campaign project."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "sharing_mode": "restricted"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Change a project's link sharing explicitly. `sharing_mode: "restricted"` unshares it (every link stops resolving) and `view` revokes an edit link; `edit` opens it for editing (may be refused on the plan: paid_plan_required). `passphrase: null` clears the passphrase. Only fields given change.
```

{% endcode %}

</details>

## flora\_list\_comment\_threads <a href="#flora_list_comment_threads" id="flora_list_comment_threads"></a>

List a project's comment threads, newest first, with each thread's status, pin position and a preview.

**Labels:** read-only

**Shown in clients as:** List comment threads

**Use when:** The user asks about feedback on a project, or you need a `thread_id` before reading, replying to or resolving a thread.

**Don't use when:** You want a thread's full messages: use [`flora_get_comment_thread`](#flora_get_comment_thread). To find threads on one node, pass `node_id` here instead of filtering the list yourself.

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `status`     | string | no       | open, resolved, or all (default). One of `open`, `resolved`, `all`.                                                                                                                  |
| `anchor`     | string | no       | canvas (pins on the canvas), generation (review threads on a generation result), or all (default). One of `canvas`, `generation`, `all`.                                             |
| `node_id`    | string | no       | Only threads pinned to this canvas node. UUID or short id (n7) from flora\_get\_canvas; unknown short ids are rejected.                                                              |
| `query`      | string | no       | Plain-text match across the threads' live comments.                                                                                                                                  |
| `limit`      | number | no       | Max items to return (default 20).                                                                                                                                                    |
| `cursor`     | string | no       | Pagination cursor from a previous call's meta.next\_cursor.                                                                                                                          |

**Returns:** A page of threads, each with its `comment_thread_id` (`cth_…`), status (`open` or `resolved`), anchor, position (`x`, `y` and the `node_id` it's pinned to), `comment_count` and a preview of its first comment, plus `meta.next_cursor` when there are more.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_projects`](https://docs.flora.ai/mcp/tools/workspaces-and-projects.md#flora_list_projects)

**Usually comes before:** [`flora_get_comment_thread`](#flora_get_comment_thread), [`flora_reply_to_comment_thread`](#flora_reply_to_comment_thread)

**Example prompt:** "What open comments are on my Spring campaign canvas?"

**Example call:**

```json
{
  "project_id": "prj_abc",
  "status": "open",
  "limit": 20
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
List one project's comment threads, newest first. Read-only. Each thread has comment_thread_id (cth_…), status (open or resolved), anchor, position (x, y and the node_id it is pinned to), comment_count and a preview of its first comment. Filter with status, anchor, node_id and query. Read a thread's messages with flora_get_comment_thread.
```

{% endcode %}

</details>

## flora\_get\_comment\_thread <a href="#flora_get_comment_thread" id="flora_get_comment_thread"></a>

Read one comment thread with its live messages, oldest first.

**Labels:** read-only

**Shown in clients as:** Get comment thread

**Use when:** You need what a thread says, or a `comment_id` to delete one comment.

**Don't use when:** You don't have the `thread_id` yet: get it from [`flora_list_comment_threads`](#flora_list_comment_threads). Never guess one.

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `thread_id`  | string | yes      | The thread (cth\_…), from flora\_list\_comment\_threads or flora\_create\_comment\_thread. Never guess one.                                                                          |

**Returns:** The thread, with each message's `comment_id` (`cmt_…`), body, author and `created_at`.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_comment_threads`](#flora_list_comment_threads)

**Usually comes before:** [`flora_reply_to_comment_thread`](#flora_reply_to_comment_thread), [`flora_resolve_comment_thread`](#flora_resolve_comment_thread)

**Example prompt:** "Read me the comment thread on the hero image."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "thread_id": "cth_123"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Read one comment thread with its live messages, oldest first. Read-only. Each message carries comment_id (cmt_…), body, author and created_at.
```

{% endcode %}

</details>

## flora\_create\_comment\_thread <a href="#flora_create_comment_thread" id="flora_create_comment_thread"></a>

Pin a new comment thread on a project canvas and post its first comment. Collaborators see it on the canvas.

**Labels:** writes

**Shown in clients as:** Create comment thread

**Use when:** The user wants to leave a new comment on the canvas or on a node.

**Don't use when:** A thread already exists for the topic: answer it with [`flora_reply_to_comment_thread`](#flora_reply_to_comment_thread). Leave out `author: "flora"`; only FLORA's own agents may post as FLORA, and any other caller gets `forbidden`.

{% hint style="info" %}
To pin a comment on a node, pass `node_id` with `x` and `y` set to the node's canvas position from [`flora_get_canvas`](https://docs.flora.ai/mcp/tools/canvas.md#flora_get_canvas). `offset_x` and `offset_y` move the pin from the node's top-left corner. Without `node_id`, the pin sits at canvas `x`, `y`.
{% endhint %}

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                                                                                    |
| ------------ | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>.                                                                     |
| `body`       | string | yes      | Plain-text comment, 1 to 10,000 characters after trimming.                                                                                                                                                                                               |
| `x`          | number | yes      | Canvas X coordinate of the pin.                                                                                                                                                                                                                          |
| `y`          | number | yes      | Canvas Y coordinate of the pin.                                                                                                                                                                                                                          |
| `node_id`    | string | no       | Canvas node to attach the pin to. UUID or short id (n7) from flora\_get\_canvas; unknown short ids are rejected.                                                                                                                                         |
| `offset_x`   | number | no       | Pin offset from the node's left edge.                                                                                                                                                                                                                    |
| `offset_y`   | number | no       | Pin offset from the node's top edge.                                                                                                                                                                                                                     |
| `author`     | string | no       | user (default) posts as the signed-in user. flora posts as FLORA and is accepted only from Flora's own FAUNA, Chat, and Create agents; every other credential receives forbidden, so omit it unless you are one of those agents. One of `user`, `flora`. |

**Returns:** The new thread's `comment_thread_id` (`cth_…`).

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_get_canvas`](https://docs.flora.ai/mcp/tools/canvas.md#flora_get_canvas)

**Usually comes before:** [`flora_get_comment_thread`](#flora_get_comment_thread)

**Example prompt:** "Leave a comment on node n7 saying the logo is too small."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "body": "The logo is too small here.",
  "node_id": "n7",
  "x": 1200,
  "y": 400
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Pin a new comment thread on a project canvas and post its first comment. Collaborators see it on the canvas. To comment on a node, pass node_id with x and y set to the node's canvas position; offset_x and offset_y place the pin relative to the node's top-left (default 0). Without node_id the pin sits at canvas x, y. Returns comment_thread_id (cth_…).
```

{% endcode %}

</details>

## flora\_reply\_to\_comment\_thread <a href="#flora_reply_to_comment_thread" id="flora_reply_to_comment_thread"></a>

Post a reply on an open comment thread.

**Labels:** writes

**Shown in clients as:** Reply to comment thread

**Use when:** The user wants to answer an existing comment.

**Don't use when:** The thread is resolved: reopen it with [`flora_reopen_comment_thread`](#flora_reopen_comment_thread) first, or a reply is rejected with `input_validation_error`. A thread whose comments were all deleted stays resolved; start a new one with [`flora_create_comment_thread`](#flora_create_comment_thread).

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                                                                                    |
| ------------ | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>.                                                                     |
| `thread_id`  | string | yes      | The thread (cth\_…), from flora\_list\_comment\_threads or flora\_create\_comment\_thread. Never guess one.                                                                                                                                              |
| `body`       | string | yes      | Plain-text comment, 1 to 10,000 characters after trimming.                                                                                                                                                                                               |
| `author`     | string | no       | user (default) posts as the signed-in user. flora posts as FLORA and is accepted only from Flora's own FAUNA, Chat, and Create agents; every other credential receives forbidden, so omit it unless you are one of those agents. One of `user`, `flora`. |

**Returns:** The new comment, with its `comment_id` (`cmt_…`).

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_comment_threads`](#flora_list_comment_threads), [`flora_get_comment_thread`](#flora_get_comment_thread)

**Usually comes before:** [`flora_resolve_comment_thread`](#flora_resolve_comment_thread)

**Example prompt:** "Reply to that thread saying I've swapped in the larger logo."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "thread_id": "cth_123",
  "body": "Swapped in the larger logo."
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Post a reply on an open comment thread. A resolved thread rejects replies with input_validation_error: reopen it with flora_reopen_comment_thread first. A thread whose comments were all deleted stays resolved; start a new one with flora_create_comment_thread. Returns the new comment with comment_id (cmt_…).
```

{% endcode %}

</details>

## flora\_resolve\_comment\_thread <a href="#flora_resolve_comment_thread" id="flora_resolve_comment_thread"></a>

Mark a comment thread resolved. Its comments are kept.

**Labels:** writes

**Shown in clients as:** Resolve comment thread

**Use when:** The user says the feedback in a thread is handled.

**Don't use when:** You want to remove a comment: use [`flora_delete_comment`](#flora_delete_comment). A guest who can only comment can't resolve threads and gets `forbidden`.

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `thread_id`  | string | yes      | The thread (cth\_…), from flora\_list\_comment\_threads or flora\_create\_comment\_thread. Never guess one.                                                                          |

**Returns:** The thread with its messages. A thread that's already resolved comes back unchanged.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_comment_threads`](#flora_list_comment_threads)

**Example prompt:** "Resolve the logo comment thread."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "thread_id": "cth_123"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Mark a comment thread resolved. Its comments are kept, and an already-resolved thread is returned unchanged. Needs thread-manage permission; a guest who can only comment receives forbidden. Returns the thread with its messages.
```

{% endcode %}

</details>

## flora\_reopen\_comment\_thread <a href="#flora_reopen_comment_thread" id="flora_reopen_comment_thread"></a>

Reopen a resolved comment thread so it accepts replies again.

**Labels:** writes

**Shown in clients as:** Reopen comment thread

**Use when:** The user wants to reply to, or revisit, a thread that's resolved.

**Don't use when:** Every comment in the thread was deleted: it stays resolved, so start a new one with [`flora_create_comment_thread`](#flora_create_comment_thread). A guest who can only comment can't reopen threads and gets `forbidden`.

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `thread_id`  | string | yes      | The thread (cth\_…), from flora\_list\_comment\_threads or flora\_create\_comment\_thread. Never guess one.                                                                          |

**Returns:** The thread with its messages. A thread that's already open comes back unchanged.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_list_comment_threads`](#flora_list_comment_threads)

**Usually comes before:** [`flora_reply_to_comment_thread`](#flora_reply_to_comment_thread)

**Example prompt:** "Reopen the logo thread; it still looks too small."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "thread_id": "cth_123"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Reopen a resolved comment thread so it accepts replies again. An already-open thread is returned unchanged. A thread whose comments were all deleted stays resolved; start a new one with flora_create_comment_thread. Needs thread-manage permission; a guest who can only comment receives forbidden. Returns the thread with its messages.
```

{% endcode %}

</details>

## flora\_delete\_comment <a href="#flora_delete_comment" id="flora_delete_comment"></a>

Permanently delete one comment from a thread.

**Labels:** writes · destructive

**Shown in clients as:** Delete comment

**Use when:** The user asks you to delete a specific comment, usually one they or FLORA posted.

**Don't use when:** The feedback is only handled: resolve the thread with [`flora_resolve_comment_thread`](#flora_resolve_comment_thread) instead. Someone else's comment returns `forbidden`. Deleting can't be undone.

**Arguments**

| Argument     | Type   | Required | Notes                                                                                                                                                                                |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `project_id` | string | yes      | Project the threads belong to (prj\_…). Use project\_id from flora\_list\_projects or flora\_create\_project. An API-issued canvas URL's /projects/\<id> segment becomes prj\_\<id>. |
| `thread_id`  | string | yes      | The thread (cth\_…), from flora\_list\_comment\_threads or flora\_create\_comment\_thread. Never guess one.                                                                          |
| `comment_id` | string | yes      | The comment (cmt\_…), from flora\_get\_comment\_thread's messages.                                                                                                                   |

**Returns:** The deletion result. Deleting a thread's last comment resolves the thread and returns `thread_resolved: true`.

**Cost:** Free. This tool doesn't spend money.

**Usually comes after:** [`flora_get_comment_thread`](#flora_get_comment_thread)

**Example prompt:** "Delete my last comment on the logo thread."

**Example call:**

```json
{
  "project_id": "prj_abc",
  "thread_id": "cth_123",
  "comment_id": "cmt_456"
}
```

<details>

<summary>Full description from the server</summary>

{% code overflow="wrap" %}

```
Permanently delete one comment from a thread. The caller can delete their own comments and FLORA comments they posted; thread managers can also delete FLORA comments. Someone else's comment returns forbidden. Deleting a thread's last comment resolves the thread (thread_resolved: true).
```

{% endcode %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/mcp/tools/usage-sharing-and-comments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
