Skip to main content
Glama

Get agent-editor workflow instructions

get_workflow_instructions
Read-only

START HERE before editing a video with the agent editor (or, where enabled, before building a game with /playable, making a faceless what-if short with /faceless-production, directing a story ad film with /drama-ads, or making a presenter reel with /reel-studio). With no args, lists the workflows; with {workflow:"vidguy-edit"} returns the editing playbook and the reference files to open (get_workflow_file) at each stage: inspect → plan → build the timeline → review frames → export after a confirmed quote → deliver. {workflow:"playable"}, {workflow:"faceless-production"}, {workflow:"drama-ads"} and {workflow:"reel-studio"} return their playbooks the same way. Free, read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workflow_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowNoWorkflow id, e.g. "vidguy-edit". Omit to list the catalog.

Output Schema

NameRequiredDescriptionDefault
filesNo
workflowNo
workflowsNo
skillMarkdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the no-arg listing behavior, the per-workflow branching, and the ordered stage pipeline (inspect → plan → build → review → export after a confirmed quote → deliver). It also states the cost profile ("Free"), which annotations do not express.

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?

Front-loaded with the activation instruction and the zero-arg case before the per-workflow cases, and every clause carries information. The parenthetical list of modes is dense and mildly hurts scannability, but no sentence is padding.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out, yet the description still characterizes the shape (catalog vs. playbook with reference files). For a single optional-param read tool, an agent has everything needed to call it and to chain into get_workflow_file.

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?

Schema coverage is 100% and the schema already gives an example id, so baseline is 3; the description goes further by enumerating the concrete workflow values and describing what each returns. It stops short of stating whether an unknown id errors or falls back, which is the only missing semantic.

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?

States a specific verb+resource pair: with no args it lists the workflows, with a workflow id it returns the playbook and staged reference files. It also draws an explicit boundary against the sibling get_workflow_file, which serves the individual reference files named in the playbook.

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

Usage Guidelines5/5

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

Opens with an imperative entry condition ("START HERE before editing a video with the agent editor") and names the alternative modes and their ids (/playable, /faceless-production, /drama-ads, /reel-studio). It also tells the agent what to do next after the playbook, namely open reference files via get_workflow_file.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources