aidemo

Overview Schema Source Related Servers Discussions Admin

Scaffold a new demo

init_demo

Scaffold a product-demo project with a starter brief and storyboard. Pass a live URL to auto-generate scenes from page headings and interaction beats from selectors, then refine narration and clicks.

Instructions

Create demos// with a starter brief + storyboard. dir is the repo to scaffold into (absolute path recommended; default: server cwd). With fromUrl the page is inspected first (no LLM): its headings become scenes and its unique selectors become the beats + a _candidates list — you then write the narration and turn the candidate hover into the real click.

Input Schema

TableJSON Schema

Name	Required	Description
`dir`	No
`name`	Yes	demo name (creates demos/<name>/)
`force`	No
`fromUrl`	No	draft the storyboard from this live page
`profile`	No	fromUrl: Chrome user-data dir (logged-in pages)
`headless`	No	fromUrl: run Chrome headless (default true)
`viewport`	No	fromUrl: viewport (default 1280x720)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`demoDir`	Yes
`briefPath`	Yes
`storyboardPath`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.14.1Sep 9, 2026

addedInput schema / properties / fromUrl

Added value: +{
+  "description": "draft the storyboard from this live page",
+  "type": "string"
+}

addedInput schema / properties / headless

Added value: +{
+  "description": "fromUrl: run Chrome headless (default true)",
+  "type": "boolean"
+}

addedInput schema / properties / profile

Added value: +{
+  "description": "fromUrl: Chrome user-data dir (logged-in pages)",
+  "type": "string"
+}

addedInput schema / properties / viewport

Added value: +{
+  "additionalProperties": false,
+  "description": "fromUrl: viewport (default 1280x720)",
+  "properties": {
+    "height": {
+      "type": "number"
+    },
+    "width": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "width",
+    "height"
+  ],
+  "type": "object"
+}

First observedv0.9.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does describe the creation of demos/<name>/ and the fromUrl inspection process, including the follow-up step of writing narration and turning candidates into clicks. However, it omits behaviors like the force parameter, error handling for existing directories, or side effects on the filesystem, leaving some gaps in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, compact sentence that front-loads the primary action and then explains optional behavior. It is efficient and avoids fluff, though the structure is somewhat run-on and could be split for clarity. It still earns a 4 for being informative without unnecessary length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters, a nested viewport object, and an output schema, the description covers the main scaffolding flow and the fromUrl mode adequately. However, it does not mention the force parameter, behavior on existing directories, or error conditions, which are relevant for an init tool. The output schema handles return values, but these operational gaps prevent a higher score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 71% parameter description coverage, so the baseline is 3. The description adds meaningful context for dir (absolute path recommended, default server cwd) and for fromUrl (explaining how headings become scenes and selectors become beats). These enrich the schema and clarify key parameters, though it does not add details for force or profile beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates demos/<name>/ with a starter brief and storyboard, which is a specific verb-resource action. It also explains the fromUrl variant that inspects a live page, distinguishing it from sibling tools like record or render. The title reinforces the purpose, leaving no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for scaffolding a new demo and explains the fromUrl flow, but it does not explicitly state when to use this tool versus alternatives or when not to use it. There is no mention of exclusions or preferred scenarios compared to siblings like record or compose, so the guidance is implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server