> 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/interactive-demo/leverage/mcp/example-prompts.md).

# Example prompts

### Video Creation

* “Create a 30 second product launch video for LinkedIn.”
* “Create launch videos for our top releases this month.”
* “Create five versions of this launch video for social, paid ads, sales outreach, web, and email.”
* “Create three ad variations based on our best campaign.”
* “Create a personalized follow-up video for Salesforce.”

***

### Analytics

* “How is my demo performing?”
* “What are my most viewed Arcades this month?”
* “Show drop-off points for my onboarding demo.”
* “Which companies engaged with my demos?”
* “Chart my top demos from the last 30 days.”

***

### Optimization

* “How can I improve this demo based on performance?”
* “Which demos should I reuse for onboarding?”
* “What product topics are buyers engaging with most?”


---

# 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/interactive-demo/leverage/mcp/example-prompts.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.