Get an idea’s recording matrix
One idea’s shoot plan: its atomic article, how each presentation format fits it, the suggested picks (and a fitting proven combo), the chosen hook structures, presentation formats (a tier list’s ranked items with their tiers, a screen share’s steps with what is on screen) and pushes, the prep per format, every written line (hooks end on an open loop, bodies open on a neutral bridge and close on a seam, calls to action stand alone), the seam report and the matrix math (“3 hooks × 2 bodies × 3 CTAs = 18 videos from 8 takes”).
Behavior
- Read-only hint
- True
- Destructive hint
- Not declared
- Idempotent hint
- Not declared
- Open-world hint
- Not declared
Parameters
| Name | Type | Requirement | Description |
|---|---|---|---|
workspaceId | string | Required | The workspace id or slug (from workspace_list). |
ideaId | string | Required | No additional description. |
Input JSON Schema
Generated from the registered input schema
{
"type": "object",
"properties": {
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "The workspace id or slug (from workspace_list)."
},
"ideaId": {
"type": "string",
"minLength": 1,
"maxLength": 200
}
},
"required": [
"workspaceId",
"ideaId"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}Call shape
Use an MCP client rather than sending this JSON directly. The client handles protocol negotiation, sessions, and authentication.
Protocol request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "shootplan_get",
"arguments": {}
}
}