Skip to main content
Glama

Choose a media workflow

get_workflow_guide
Read-onlyIdempotent

Returns required inputs, ordered steps, example requests and review criteria for eight supported Magic Hour workflows. Use when planning a generation, not to run one. Requires authentication but does not check account eligibility or spend credits.

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": {
      "workflow": "<workflow>"
    },
    "name": "get_workflow_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowYesChoose the workflow matching the task and supplied inputs. Returns static planning guidance, not an account eligibility or cost quote.

Output Schema

NameRequiredDescriptionDefault
inputYesRequired source media and other inputs.
stepsYesOrdered upload, creation and retrieval steps.
titleYesHuman-readable workflow purpose.
reviewYesOutput checks and workflow-specific limitations.
guidanceYesAccount, cost, recovery and usage caveats.
workflowYesRequested workflow identifier.
follow_upYesHow to reuse or edit an accepted result.
product_urlYesRelevant Magic Hour product page.
api_docs_urlYesAPI documentation for the selected workflow.
creation_toolNoMCP creation tool, or null for general API integration guidance.
evaluation_urlYesGuidance for evaluating completed media outputs.
example_requestYesExample user request for this workflow.
starter_recipes_urlYesAPI starter recipes.
models_and_costs_urlYesDocumentation of model constraints and credit costs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / workflow / description
      Added value: +"Choose the workflow matching the task and supplied inputs. Returns static planning guidance, not an account eligibility or cost quote."
    • addedOutput schema / description
      Added value: +"Static workflow planning guidance. Does not verify account access, eligibility, current price or output quality."
    • addedOutput schema / properties
      Added value: +{
      +  "api_docs_url": {
      +    "description": "API documentation for the selected workflow.",
      +    "type": "string"
      +  },
      +  "creation_tool": {
      +    "description": "MCP creation tool, or null for general API integration guidance.",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "evaluation_url": {
      +    "description": "Guidance for evaluating completed media outputs.",
      +    "type": "string"
      +  },
      +  "example_request": {
      +    "description": "Example user request for this workflow.",
      +    "type": "string"
      +  },
      +  "follow_up": {
      +    "description": "How to reuse or edit an accepted result.",
      +    "type": "string"
      +  },
      +  "guidance": {
      +    "description": "Account, cost, recovery and usage caveats.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "input": {
      +    "description": "Required source media and other inputs.",
      +    "type": "string"
      +  },
      +  "models_and_costs_url": {
      +    "description": "Documentation of model constraints and credit costs.",
      +    "type": "string"
      +  },
      +  "product_url": {
      +    "description": "Relevant Magic Hour product page.",
      +    "type": "string"
      +  },
      +  "review": {
      +    "description": "Output checks and workflow-specific limitations.",
      +    "type": "string"
      +  },
      +  "starter_recipes_url": {
      +    "description": "API starter recipes.",
      +    "type": "string"
      +  },
      +  "steps": {
      +    "description": "Ordered upload, creation and retrieval steps.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "title": {
      +    "description": "Human-readable workflow purpose.",
      +    "type": "string"
      +  },
      +  "workflow": {
      +    "description": "Requested workflow identifier.",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[
      +  "workflow",
      +  "title",
      +  "input",
      +  "product_url",
      +  "api_docs_url",
      +  "steps",
      +  "example_request",
      +  "follow_up",
      +  "review",
      +  "models_and_costs_url",
      +  "evaluation_url",
      +  "starter_recipes_url",
      +  "guidance"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this readOnly/idempotent/non-destructive, but the description adds facts the annotations cannot express: it requires authentication, performs no account eligibility check, and spends no credits. Those are exactly the misconceptions an agent might otherwise have about a planning call. It stops short of describing output shape or rate/error behavior, which the output schema largely covers.

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

Conciseness5/5

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

Three sentences, zero filler, with what-is-returned front-loaded and the usage boundary immediately after. Nothing could be deleted without losing routing or expectation-setting information.

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

Completeness4/5

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

Return contents, auth requirement, and the cost/eligibility caveat are all covered, and an output schema exists so return formatting need not be spelled out. Only minor gap is any indication of error behavior for an unsupported workflow value.

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

Parameters5/5

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

With 100% schema coverage and a single enum parameter, the schema already documents selection, yet the description still adds the count ('eight supported workflows') and frames the parameter's purpose as task/input matching rather than execution. Meaningful reinforcement without redundancy.

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 and resource ('Returns required inputs, ordered steps, example requests and review criteria') scoped to 'eight supported Magic Hour workflows', and explicitly separates itself from execution tools with 'Use when planning a generation, not to run one.' An agent can tell this apart from the create_*/edit_* siblings immediately.

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

Usage Guidelines4/5

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

Gives a clear when ('planning a generation') and a when-not ('not to run one'), which is the key routing decision for a planning tool. It does not name a specific execution sibling as the alternative, but the exclusion is unambiguous.

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.