---
title: Prompts
description: Run a playbook, or insert the context of a brand, from the slash menu of your AI client and of the Adgent.
---

Your playbooks and your brands show in the slash menu of your AI client, as **MCP prompts**. You pick one by name. You do not have to describe the task and hope that the agent finds the correct playbook.

A prompt is yours to pick. The agent cannot pick a prompt itself. The agent can still find and load a playbook during a task, with [`skill_list`](/mcp/tools/skill-list) and [`skill_get`](/mcp/tools/skill-get). The menu adds a deliberate way for you to start.

## Playbooks

Each playbook of your organization is one prompt. Its name is the slug of the playbook, for example `weekly-report`. The menu shows its title and its description.

When you pick a playbook, your client inserts the instructions of the playbook as your message. The agent then runs them. [Reuse a playbook](/mcp/tools/reuse-a-playbook) shows how to write a playbook.

## Brands

Each brand of your organization is one prompt too. Its name starts with `brand:`, for example `brand:acme-running`, so that you can tell a brand from a playbook.

When you pick a brand, your client inserts the context of the brand: its identity, its voice, its guidelines and its messaging. A section that nobody wrote is left out. So the next text that the agent writes is already on brand.

The files and the ad accounts of the brand are not inserted. They stay one call away, with [`brand_get`](/mcp/tools/brand-get). A pick from a menu does not put a list of links in your conversation. [Describe a brand](/mcp/tools/describe-a-brand) shows how to write a brand.

## Which prompts you see

Your client shows the prompts that its token can read:

- Playbooks need the scope `skill:read`.
- Brands need the scope `brand:read`.

The consent screen grants all the scopes that your client asks for, together. [Auth & scopes](/mcp/auth#scopes) explains this.

AdCrunch does not tell your client when the list changes. A playbook or a brand that you add later shows the next time that your client asks for the list.

## In the Adgent

The Adgent in the console has the same menu for playbooks. It does not show brands.

1. Type `/` in the message box, and pick a playbook.
2. The message box holds the handle of the playbook, for example `/weekly-report`.
3. Add words to narrow the task, for example `/weekly-report for the Acme account`, and send.

The Adgent receives the full instructions of the playbook, followed by your words. The conversation shows the handle that you typed.

## Where to find the menu

Each client puts the menu in its own place. Most clients show it when you type `/` in the message box. A client that does not support MCP prompts shows no menu. The tools still work in that client.