MCP Prompt Library — What to Ask Your Walnut Connector
Ready-to-paste prompts for the Walnut MCP server, organized by role — sales, presales, marketing, RevOps, and admin — plus library organization, member management, multi-tool workflows, and recurring routines.
MCP Prompt Library — What to Ask Your Walnut Connector
Once the Walnut MCP is connected, the hard part isn't the setup — it's knowing what's worth asking.
The connector does two kinds of work. It answers questions about your demo performance and how your content is set up, and it gets things done — building and publishing Demos, translating Templates, filing demos into folders, tagging in bulk, locking down who can open a Demo, inviting members, reassigning a leaver's work. Anything that changes your data shows you a preview and waits for your go-ahead first, so you can ask boldly.
These are prompts that work. Copy one, swap in your demo names, people, and dates, and go. Every prompt below runs against your own account, in Claude, ChatGPT, Codex, or Microsoft Copilot Studio.
Start here
Four prompts to run on day one, in order.
Check my Walnut connection and tell me what data and actions you can access.
Give me a summary of our demo performance over the last 90 days. Include total sessions, completion rate, bounce rate, and average interactions.
Which five demos got the most sessions in the last 90 days, and how do their completion rates compare to each other?
Search my library and tell me how many Templates, Demos, Playlists, and Deal rooms I have, and who owns the most.
If those four work, everything below will.
Build and share Demos
Ask for a Demo in plain words. Your assistant asks how it will be used and who it's for, offers anything you already have that fits, and otherwise builds a new one from your Screens Library: you approve a short outline, review the plan, and get a Template plus a published Demo link. For the full walkthrough, see Build a guided Demo with your AI assistant.
Build a new Demo
Build a Demo for Acme's VP of Sales to watch after yesterday's call.
I need a live call Demo of our reporting features for a RevOps lead at Globex.
Build a website embed Demo that shows marketing leaders how our campaign builder works.
If you've connected a CRM, a call recorder, or a calendar too, name the prospect and your assistant uses what those tools know to suggest how the Demo will be used and who it's for.
While you review the plan, ask for changes using its screen numbers:
In the plan, reword step 3 so it talks about saving time, and swap screen 5 for the approvals dashboard.
Reuse what you have
Do we already have a Demo about security for IT buyers? If so, give me a link I can send.
Publish a new link from the Platform Tour Template for Initech, with their company name in it.
Personalize and update
The Onboarding Template says "Demo Inc" everywhere. Make that a variable so each Demo can show the customer's company.
Republish the Acme Demo so it picks up the latest changes to its Template.
Translate
Translate the Enterprise Overview Template into German, guides and screen text. Keep "Walnut" in English.
How is the French translation of the Onboarding Template going? Republish the Demo when it's done.
Does the Platform Tour Demo already have Japanese? If so, give me that link.
Sales
Know the story before the call
Pull all sessions for the demo "Enterprise Overview" in the last 30 days. Which countries are they coming from, and what share reached the end?
Show me every completed session from external viewers in the last 7 days, with the demo name and interaction count. Sort by interaction count.
Find the people worth calling back
List external sessions from the last 14 days where the viewer completed the demo and had more than 5 interactions. Give me demo name, date, and country.
Which demos in the last 30 days have external viewers who submitted the lead form? Break it down by demo.
Sanity-check a demo you're about to send
Compare "Security Deep Dive" and "Platform Tour" over the last 60 days — sessions, completion rate, bounce rate, and average screen views. Which one should I send to a technical buyer?
Weekly self-review
Summarize my team's demo activity for last week versus the week before. Call out anything that moved more than 20%.
Presales and sales engineering
Spot where prospects drop off
For "Enterprise Overview" in the last 90 days, what's the average screen views per session? The demo has 12 screens — what does that tell us about drop-off?
Show me bounced sessions for our top 5 demos over the last 60 days as a share of total sessions for each. Which demo has the worst opener?
Compare audiences
Group sessions from the last quarter by demo name and user type. Which demos are mostly internal previews rather than real prospect views?
Compare embedded sessions to standalone link sessions over the last 90 days — volume, completion rate, and average duration. Where should we invest?
POC and technical evaluation follow-through
Pull every session for demo ID abc-123 since October 1st with the full field list. Summarize the engagement pattern — are viewers returning, or is this all first-touch?
Marketing and demand gen
Campaign performance
Group demo sessions by date for the last 30 days and describe the trend. Did anything spike, and on which demos?
Compare demo performance for the last 30 days against the 30 days before that. Totals, completion, bounce, and the top 5 demos in each period.
Where the traffic actually comes from
Break down the last 90 days of external sessions by country. Which markets are we underserving relative to session volume?
Show me only embedded sessions from the last 60 days, grouped by demo. Which website placements are pulling their weight?
Lead capture health
For the last 90 days, pull sessions with the lead form fields. What's our lead form conversion rate — submitted over opened — and how does it vary by demo?
Reporting on autopilot
Write a 5-bullet demo performance summary for our VP of Marketing covering last month. Lead with what changed, not what's steady. Include one recommendation.
RevOps and analytics
The monthly review
Give me the demo sessions summary for last month. Then compare it to the same month last year and flag every metric that moved more than 15%.
Group last quarter's sessions by demo name. Build me a table with sessions, and rank demos by volume. Then tell me which demos are in the long tail and probably worth retiring.
Data quality and hygiene
What share of our sessions in the last 90 days are internal versus external? If internal is above 20%, tell me which demos drive it.
How many sessions in the last 90 days have an identifiable viewer — a lead form or email gate? What's our identification coverage?
Content lifecycle
Which demos had sessions in the first half of the last 12 months but none in the last 90 days? Those are candidates for archiving.
Group the last 180 days by demo name and by month. Which demos are trending down?
Export for the warehouse
Pull the last 1,000 external sessions with the fields id, demo_name, started_at, is_completed, interaction_count, geo_country_name. Format as CSV.
Organize your library
The connector can search and reorganize your whole library — Templates, Demos, Playlists, Deal rooms, and Deal room templates. Anything that writes (foldering, tagging, renaming, archiving, reassigning) runs on a preview-then-confirm flow: you'll see the exact list and a count first, and nothing changes until you say go.
Find things
Search my library for every Demo with "Acme" in the name and tell me who owns each one.
List all Playlists that use the Choose Your Own Adventure layout, with their owner and folder.
Find every Demo that hasn't been played by a prospect in the last 6 months, grouped by owner.
Foldering
Create a folder called "Archive 2025" under our "Sales Demos" folder.
Move every Demo tagged "q1-campaign" into the "Campaigns / Q1" folder. Show me what will move before you do it.
Reparent the "Old EMEA" folder under "Archive 2025", and move its whole subtree with it.
Tagging
Tag every Demo created before January 1 that hasn't been played since with "stale-review". List them first, and only create the tag if it doesn't already exist.
Remove the "draft" tag from every Template in the "Published" folder.
Renaming in bulk
Find every item with "2024" in its name and replace it with "2025". Preview the before-and-after list first.
Rename the Demo "Platform Tour v3 FINAL" to "Platform Tour — Enterprise".
Archiving and cleanup
Archive every Demo not played by a prospect in the last 12 months. Show me the list first — and flag any that are still live inside a published Playlist or Deal room before archiving them.
Restore the Demos I archived last week that have "Acme" in the name.
Sharing and duplicating
Share every Template in the "Onboarding" folder with the whole company.
Give the Sales Engineering group edit access to everything in the "Q4 Demos" folder. Show me the list first.
Duplicate the "Enterprise" Deal room template and call it "Enterprise — EMEA".
Reassigning ownership
Transfer every Demo and Template owned by [departing rep] to [their manager]. Show me the count and a sample before confirming.
Move ownership of everything in the "West Region" folder to [name].
Review and change sharing settings
The connector can audit how your Playlists, Deal rooms and Deal room templates are shared — expiry, access code, who can open them, the email gate, non-work emails, allowed and blocked people and domains, and view-notification emails — and change any of those settings for one item or a whole folder at once. Writes use the same preview-then-confirm flow as the rest of the library tools: you'll see each item's from → to, plus anything the tool left out and why, before anything is written. Access codes are never read back, and a single write is capped at 100 items — narrow the selection if your filter matches more.
It works for Playlists, Deal rooms, and Deal room templates (templates are included only when you name them, since a template's settings are what new Deal rooms made from it start with). Individual Demos have their own settings and aren't covered by these prompts. These are the settings for opening the item as a whole; page-level restrictions inside a Deal room aren't changed here.
Audit who can open what
List every Playlist and Deal room anyone with the link can open. Include owner and expiry.
Which Deal rooms never expire? Group by owner.
Show me every Playlist still open to acme.com — the allowed list, the expiry, and whether an access code is set.
Which Playlists and Deal rooms have an access code set? I don't need the code, just the list.
Which Deal room templates ask for an email before opening, and which don't? New rooms made from them will inherit that.
Expiry dates
Set every Playlist in the "Q3 Campaigns" folder to expire on 2026-12-31. Preview first.
Remove the expiry from the Deal room "Acme — Enterprise Rollout".
Access codes
Turn on an access code for the Deal room "Acme — Enterprise Rollout". I'll give you the code — [code] — don't make one up.
Turn off the access code on every Playlist tagged "self-serve".
Who can open an item
Restrict the Playlist "Security Deep Dive" to only @acme.com and jane@contoso.com.
Open the Deal room "Public Launch" to anyone with the link.
On every Deal room owned by [name], add @partner.com to the allowed list — don't replace what's already there.
On the Playlist "Pricing Teardown", block @competitor.com from opening it.
Email gate and non-work emails
Turn the email gate on for every Playlist in the "Outbound" folder.
Allow non-work emails on the Deal room "SMB Pilot".
View-notification emails
Email me and [teammate] whenever the Deal room "Acme — Enterprise Rollout" is viewed.
Stop emailing anyone when the Playlist "Public Launch" is viewed.
On every Deal room owned by [name], also email the CRM deal owner on each view.
Demo settings
The same kind of audit and fixes work for Demos, plus their link options and Buyer Xpert. A single change covers up to 100 Demos.
Which of my Demos never expire? Group them by folder.
Which Demos are still open to acme.com? We lost the deal.
Set every Demo in the "Q3 Campaigns" folder to expire on December 31.
Only let people from @acme.com open the Acme Demos.
Email me and the deal owner whenever someone views the "Enterprise Overview" Demo.
Turn off the guides toolbar on all Demos tagged "website", and give me the new share links.
Make our public product tour Demo readable by AI and search crawlers.
Admin, seats, and people
Seat management
What's our current Walnut seat utilization? Break it down by role and tell me how much headroom we have.
Are we close to any seat limit? If remaining editor seats are under 5, say so plainly. Include any pending invites that are holding seats.
Adoption and onboarding
List our Walnut users with their role and last login. Who hasn't logged in during the last 60 days?
Show me users and their creation counts over the last 90 days. Who are our power creators, and who has a seat but has created nothing?
Invite and manage members
Invite alice@acme.com as an editor and bob@acme.com as a viewer. Tell me first whether we have the seats.
Here are 12 new hires — invite them all as presenters: [paste emails]. If we're short on seats, tell me by how much instead of inviting anyone.
Show me every pending invitation and which ones have already expired.
Cancel the pending invite for the misspelled address typo@acme.com so I can re-send it.
Promote [name] from viewer to editor.
Change [name] to company admin.
When someone leaves
Offboarding transfers everything a person owns to a colleague and then removes their access. It's irreversible, so the connector will preview what they own and ask you to confirm explicitly.
[name] is leaving. Show me everything they own across demos, templates, folders, and the rest — don't change anything yet.
Offboard [departing member] and transfer all of their work to [recipient]. Walk me through what moves before you do it.
Quarterly license review
Combine our seat utilization with user activity over the last 90 days. Build me a case for either right-sizing our contract or expanding it.
Multi-tool workflows
MCP gets more interesting when Walnut sits alongside your other connectors. These prompts assume you've connected the other tool too.
Pre-meeting brief — Walnut + calendar
Look at my calendar for tomorrow. For each external meeting, check whether we have Walnut demo sessions from that company's domain in the last 30 days, and give me a one-paragraph brief per meeting.
Post-call follow-up — Walnut + CRM
For each open opportunity in my pipeline closing this quarter, pull the Walnut sessions tied to that account's demos in the last 45 days. Flag any deal with no demo engagement at all.
Weekly digest — Walnut + Slack
Pull last week's Walnut demo summary, write it as a 4-bullet Slack post for #revenue with one clear takeaway, and post it.
Board-deck numbers — Walnut + spreadsheet
Pull demo sessions grouped by month for the last 12 months, write it into a new sheet with columns for month, sessions, and completion rate, and add a line chart.
Objection follow-up — Walnut + call recordings
Find the objections raised in yesterday's calls. For each one, tell me which of our demos best addresses it based on the demo names and their engagement data.
Recurring routines
If your AI client supports scheduled or repeating tasks, these are worth automating.
| Cadence | Prompt |
|---|---|
| Every Monday, 8am | "Pull last week's Walnut demo summary. Compare to the prior week. Post a 4-bullet digest to #revenue with one recommendation." |
| Daily, 7am | "Check yesterday's Walnut sessions for external viewers who completed a demo with 5+ interactions. If there are any, DM me the list." |
| First of the month | "Generate the monthly Walnut demo performance report: totals, averages, top 10 demos, top 10 countries, and month-over-month deltas." |
| Monthly | "Find Demos not played by a prospect in the last 12 months and list them as archive candidates — don't archive anything, just show me the list." |
| Weekly | "List my Demos and Deal rooms that expire in the next 14 days, with their share links, so I can extend the ones still in play." |
| Quarterly | "Pull Walnut seat utilization and 90-day user activity. Draft a license right-sizing recommendation, and list seats held by people who never log in." |
How actions work
Reading data is instant. Anything that changes your account is deliberately a two-step move.
Broad changes get a preview first. Ask to tag, move, rename, archive, share, or reassign everything that matches a filter, and the connector comes back with the true count and a sample of exactly what it matched — before touching anything. Read it, then tell it to go ahead. When you name the exact items, small changes happen right away. Settings changes, publishing a Demo, and starting a translation always show you a preview first.
Building a Demo waits for your go-ahead. You approve the outline, then review and approve the plan, and Walnut builds from exactly what you approved.
Names get resolved to the real thing. When you name a demo, a folder, or a person, the connector looks up the exact item. If the name is ambiguous, it shows you the candidates instead of guessing.
Big blast radii are capped. A single bulk action won't run against more than 500 items, or more than 100 for a settings change — if your filter matches more, narrow it (by folder, tag, owner, or date) and try again.
The irreversible ones ask twice. Offboarding a member transfers all their work and cuts their access for good; archiving a demo that's still reachable by buyers warns you first. Both need an explicit confirmation — the connector will never set that flag for you.
Getting better answers
Always name a date window. Without one you get the last 365 days (90 for user activity), which buries recent changes. "Last 30 days" or "since October 1" both work.
Say "external" when you mean prospects. By default the assistant sees internal previews too, and they distort every rate you care about.
Ask for grouped counts over long windows. "Group by demo name for the last 6 months" returns one row per demo. Asking for raw sessions over the same window hits the 1,000-row cap and gives you a truncated picture.
Name the item type when you organize. "Archive Demos not played in a year" is cleaner than "archive old stuff" — the connector works across Templates, Demos, Playlists, Deal rooms, and Deal room templates, so tell it which.
Always read the preview before you confirm a write. The count is the tell — if "tag every stale demo" previews 4,000 items, your filter is too broad. Narrow it and preview again.
Give it the benchmark. The assistant knows your numbers but not what "good" looks like. Paste a row from the Demo Analytics Cheat Sheet into the prompt and ask it to judge against that.
Name the audience for the output. "Write this for a VP of Sales" produces a very different — and more useful — answer than no framing at all.
Ask it to show its work. "Tell me which date range and filters you used" catches the cases where it guessed differently than you meant.
Related
Walnut MCP Server — setup and troubleshooting
What you can do with the Walnut MCP — every capability, and who can use it
Demo Analytics Cheat Sheet — benchmarks for reading the results
Integration Recipes — for turning a one-off question into a scheduled job