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

# Available Tools

### Video and Brand Kit

| Tool                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `create_brand_kit`      | Create a Brand Kit from a website domain. Extracts colors, logos, fonts, and style guidelines.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| `add_brand_kit_source`  | Add a URL source (blog post, landing page, docs) to enrich a Brand Kit's branding data.                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| `list_brand_kits`       | List Brand Kits in your workspace. Check status before creating a video.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| `create_video`          | Generate a video from a prompt, a preset style (`product-release`, `explainer`, `sales`, or `social-media`), screenshots, website URLs, or existing Arcade demos. Doesn't require a Brand Kit — uses your named kit, your workspace's default, or your only kit automatically if you skip it. Also takes aspect ratio, a quality tier (Light/Medium/High), a length from 15s to 120s (a lower ceiling than the composer's plan-based caps), up to 20 existing video files, up to 3 website URLs, and a public YouTube link as a style reference. |
| `edit_video`            | Change a video that MCP itself made — `create_video` or an earlier `edit_video` — anywhere in your workspace, not just earlier in the same chat: new wording, pacing, a scene, colors, the format, or reverting to an earlier version. Only works on videos made through this MCP; it can't touch a video made directly in the Arcade editor.                                                                                                                                                                                                    |
| `get_generation_status` | Check the status of a video generation in progress.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| `preview_video`         | Show the finished video inline, and return both the exported MP4's own URL and a link to open it in the Arcade editor. Available on Claude and ChatGPT; other clients get a link instead.                                                                                                                                                                                                                                                                                                                                                        |
| `upload_image`          | ChatGPT only. Save an image you attached in chat (PNG, JPEG, WebP, or GIF, up to 10MB, up to 10 per call) to your workspace media library, returning its Arcade image ID for use as a `create_video`/`edit_video` input — this is how a ChatGPT conversation's attached screenshots reach a video; `create_video` itself doesn't take screenshots directly, and no other client can attach images this way.                                                                                                                                      |
| `get_credits`           | Check your workspace's AI-video credit balance, or what a specific generation (model and length) would cost before you commit to it.                                                                                                                                                                                                                                                                                                                                                                                                             |

### Using an existing demo as source material

| Tool         | Description                                                                                                                    |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| `list_demos` | Browse your existing interactive demos, and use one as source material for a new video.                                        |
| `search`     | Search your workspace's existing interactive demos by name or keyword, to find one to use as source material or reference.     |
| `fetch`      | Get one interactive demo's full record — title, description, and share URL — by the id returned from `search` or `list_demos`. |

{% hint style="info" %}
Looking for the tools that report on your interactive demos' performance instead — views, completions, drop-off, trending demos? Those live on the Interactive Demo side — see [Available Tools](https://docs.arcade.software/kb/interactive-demo/leverage/mcp/available-tools/).
{% endhint %}


---

# 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.arcade.software/kb/ai-video/mcp/available-tools.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.
