MCP / Tools / Core Project / template_list

template_list

readbetaauth: project:readapproval: neverstatus: v1

List available BeatBandit templates and return a compact project creation next-action template. Use each template's `project_create_mode` (same as `mode`) when creating a new project, and pass selected `template_settings` values such as advertisement runtime and placement when the template exposes settings.

When to use

  • Use when the caller needs to discover BeatBandit template modes.
  • Use when the caller needs to inspect template settings before creating a project, for example advertisement runtime or placement.
  • Use the returned `project_create_mode` field directly with `project_mutate(create)`.
  • After choosing a template, follow the returned `start_payload_template` / `next_actions` to call `project_mutate` with `operation=create`, the selected `project_create_mode`, a project name, and any desired `template_settings` from the selected template.

When not to use

  • Do not use for reading one project or one full screenplay.
  • Do not set `include_project=true` when creating from a listed template; use compact create plus resource links.

Examples

  • “List the templates I can use for a new project.”
  • “Show the templates and tell me what settings the video advertisement template supports.”

Anti-examples

  • Open my existing project and show its screenplay.

Backend capabilities

template.list

Linked resources

Tool calls may return resource_links pointing at these resource families.

Input schema

template_list input
{
  "$ref": "./template.list.input.json"
}

Output schema

template_list output
{
  "$ref": "./template.list.output.json"
}
← All toolsv1 · query_tool