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

# What you can ask

> Things to try once your MCP client is connected to Fandom.

Talk to it like a colleague. Names, @handles and links are enough: your client never needs an id, and every answer says how it read you.

## Explore an audience

* "Who are mothers in their late 30s who care about online privacy, on YouTube?"
* "Map the home espresso audience. Who are they?"
* "Show me the audience of @yourfavouritecreator." Or paste a channel or video link.
* "Who buys from yourbrand.com?" A website is read for who its customers are.
* "Split that map by life stage." Or by themes, groups, or something of your own, like "price sensitivity".
* "Open the second group and split it again."
* "In the specialty coffee group, which small channels have the highest fan density?"
* "What else do these fans subscribe to?"
* "Compare espresso machines and grinders on this map."
* "Only brand-safe channels, please."
* "Write an audience report and save it."
* "Save those channels as an audience called Espresso fans."

> [accordion] What an answer looks like
>
> A real map of home espresso, shortened:
>
> **36.9K people** comment on its own channels; 6.5M across all 110 channels on the map.
>
> | Group | Channels | People | Reach | Fan density |
> | - | - | - | - | - |
> | Culinary Technique Explorers | 34 | 1.4M | 23% | 10.2x |
> | Science DIY Enthusiasts | 36 | 2.2M | 30% | 8.8x |
> | Tech Gadget Reviewers | 20 | 3.3M | 33% | 6.4x |
>
> Reach is the share of the audience that also comments on a group's channels; fan density is how many times more common the audience is there than across YouTube. Answers link to the same map in Fandom, so you can pick it up there. A map's groups keep their names when you come back to it, so you can ask about a group by name.

## Build an inclusion list

* "Build an inclusion list of 200 channels for espresso gear buyers, US only, at least 25K subscribers."
* Paste a brief or an email: "Turn this into an inclusion list."
* "How much data do these seed channels have?"
* "Is it ready? Show me the top 20 and anything flagged."
* "Why is this channel on the list?"
* "Give me the Google Ads file."
* "Raise the minimum to 100K subscribers and run it again."

Downloads come as the Google Ads placements file, the full list, or a workbook. Links last 24 hours. A list run is paid, so your client asks before starting one.

## Work on a project

* "Start a project to understand the home espresso audience."
* "What do they say about grinders?"
* "What are they passionate about?"
* "Make the report, add a section on how often top channels post, and give me a link to share."
* "Make an inclusion list of the top 100 channels from this project."
* "Write a creator report on my channel. What do my fans want next?"

## Keep an eye on something

* "Every week, tell me which of these channels' fans mention our product."
* "What did the latest run find?"

## Run campaigns

* "What's in my workspace?"
* "Create a Demand Gen campaign for my brand using the Espresso fans audience, then show me the targeting."
* "Remove anything about travel from the targeting."
* "Create it in Google Ads."
* "How did my campaigns do over the last 30 days?"

Google Ads campaigns are always created paused, and their targeting goes over when you sync the campaign in Fandom.

## Good to know

* **Big jobs take a few minutes.** Reports and lists keep working while your client checks back. If it loses track, ask "is it ready?"
* **Several workspaces?** Fandom uses the one you used last from that app. Name another to switch.
* **People means people who comment,** not everyone who watches.
* **Your client asks before anything paid or anything that changes your account.** Maps and reports it just runs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.