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

# Available tools

> Generally available Bloom MCP capabilities and their roles.

After authentication, an MCP client discovers the Bloom tools available to the connected account through `tools/list`. That runtime response contains each tool's current description and input schema and is the exact source of truth.

The tools below are generally available. Additional capabilities can appear during a rollout, so this page is a capability map; it is not a complete inventory for every account.

## Brands

| Tool                           | Use it to                                                                                                             |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
| `bloom_onboard_brand`          | Create a Brand from source evidence. Accepts `sources` or a single-URL compatibility input.                           |
| `bloom_get_brand`              | Read one Brand's lifecycle status and current profile. Use `wait: true` after onboarding.                             |
| `bloom_list_brands`            | List accessible Brands with pagination and optional workspace or URL filtering.                                       |
| `bloom_delete_brand`           | Delete an accessible Brand after explicit user intent.                                                                |
| `bloom_update_brand_logo`      | Replace the logo of an older Brand that uses Visual DNA, then start the required re-analysis.                         |
| `bloom_open_logo_upload_ui`    | Open an inline picker for a local primary-logo file when the client supports MCP Apps.                                |
| `bloom_create_logo_upload_url` | Create a short-lived signed upload URL for a local primary-logo file used by the older Visual DNA compatibility flow. |

For new Brands, use `sources` to combine website, Instagram, and file evidence and optionally provide `instructions`. A plain `url` also builds a Brand Skill, but is retained for integrations that submit one website or Instagram profile. Adding `logo_url` switches that request to the older explicit-logo onboarding workflow.

Brand onboarding is asynchronous. A successful `bloom_onboard_brand` call does not mean the Brand is ready; use `bloom_get_brand` with the returned ID until its status becomes `ready`, `logo_required`, or `failed`.

## Image creation and retrieval

| Tool                      | Use it to                                                                                          |
| ------------------------- | -------------------------------------------------------------------------------------------------- |
| `bloom_generate_image`    | Start one Brand-aware generation with optional variants and reference images.                      |
| `bloom_get_image`         | Retrieve one generated, uploaded, or source image; use `wait: true` for an in-progress generation. |
| `bloom_list_images`       | List images or retrieve several known image IDs in one call, with optional waiting.                |
| `bloom_edit_image`        | Edit a completed generated or uploaded image with a natural-language instruction.                  |
| `bloom_resize_image`      | Reflow a completed raster image to another supported aspect ratio.                                 |
| `bloom_remove_background` | Create a transparent PNG from a completed raster image.                                            |
| `bloom_vectorize_image`   | Convert suitable raster artwork into SVG.                                                          |
| `bloom_delete_images`     | Delete one or more accessible images after explicit user intent.                                   |

Generation and transformation tools return new image IDs before the work finishes. Retrieve the returned IDs and check for `completed` or `failed` status before presenting a result.

## References and uploads

| Tool                            | Use it to                                                                                                |
| ------------------------------- | -------------------------------------------------------------------------------------------------------- |
| `bloom_search_user_images`      | Search one Brand's Library by visual meaning and return image IDs suitable as generation references.     |
| `bloom_find_reference_ads`      | Search Bloom's curated reference-ad library and return IDs that can be passed to `bloom_generate_image`. |
| `bloom_upload_image`            | Import a publicly reachable image URL into one Brand Library.                                            |
| `bloom_open_upload_ui`          | Open an inline picker for local reference or edit-subject files when the client supports MCP Apps.       |
| `bloom_create_image_upload_url` | Create 1–10 short-lived signed URLs for local image uploads in a headless workflow.                      |

Search results are candidates, not automatic user approval. Show them when the user has asked to choose; select them directly only when the user has delegated that choice.

## Workspaces, credits, and account

| Tool                    | Use it to                                                          |
| ----------------------- | ------------------------------------------------------------------ |
| `bloom_list_workspaces` | List the personal and team workspaces accessible to the caller.    |
| `bloom_check_credits`   | Read the remaining credit balance for a selected workspace.        |
| `bloom_get_account`     | Confirm which Bloom account authenticated the current MCP session. |

Brand and image results include workspace identity where it is needed for disambiguation. Creation tools default to the personal workspace only when their live schema says the workspace argument is optional.

## Read the live schemas

Tool names alone are not sufficient to construct a request. Before calling a tool, read its current:

* description and workflow guidance;
* required and optional input fields;
* output schema;
* read-only, destructive, and idempotency annotations; and
* MCP Apps metadata, when present.

Do not assume a tool exists because it appears in a previous conversation or cached copy of this page. Refresh `tools/list` after reconnecting or when Bloom reports that the available capabilities changed.

Continue with the [MCP quickstart](/docs/mcp/getting-started), [Generate images](/docs/guides/generate-images), or [MCP troubleshooting](/docs/mcp/troubleshooting).