Demo Script Builder
demo_script_builderBuilds a timed demo script from the demo type, persona, use case, must-show features, and named pains, mapping each step to pains with spoken lines, discussion, close, and follow-up.
Instructions
Helps you decide what to show in a demo, and in what order. You give the demo type, the persona and the use case, plus the features you must show and the pains you name. You get a timed run from opening to close, with spoken lines and a step for each feature tied to the pains, then discussion, close and follow up lines and sector notes. The answer says where each step came from and what it did not get. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of sales_enablement_content when you need a timed product demonstration tied to the use case.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"demo_type": "<demo_type>",
"your_solution": "<your_solution>"
},
"name": "demo_script_builder"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| attendees | No | Other attendees and their roles. Format is text. For example, "procurement lead and security reviewer". | |
| demo_type | Yes | Type of demo. Format is text using one of the listed labels. For example, "first_look". | |
| your_sector | No | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| demo_duration | No | Demo duration in minutes. Format is a JSON number. For example, 12. | |
| your_solution | Yes | Your product/solution. Format is text. For example, "invoice review service". | |
| desired_outcome | No | What you want to achieve from this demo. Format is text. For example, "resolve invoice exceptions before month-end". | |
| key_pain_points | No | Pain points to address in demo. Format is text. For example, "invoice exceptions delay month-end close". | |
| known_objections | No | Known objections to address. Format is text. For example, "The reviewer asked who owns unresolved exceptions.". | |
| primary_audience | No | Primary demo audience (role/persona). Format is text. For example, "finance leaders at manufacturers". | |
| customer_industry | No | Customer industry. Format is text. For example, "manufacturing". | |
| competitor_context | No | Competitor being displaced or compared. Format is text. For example, "renewal decision depends on a documented approval process". | |
| must_show_features | No | Features that must be demonstrated. Format is text. For example, "exception queue and approval history". |