Skip to main content
Glama

list_commands

Read-only

Search FilmCraft engine commands by keyword to find IDs, labels, and parameters for effects, color, audio, captions, and keyframes; pair with run_command when no dedicated tool exists.

Instructions

Search FilmCraft's 650+ engine commands (id, label, params). Use with run_command for anything without a dedicated tool (effects, color, audio, captions, keyframes…).

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": {
      "filter": "<filter>"
    },
    "name": "list_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterYesSubstring, e.g. 'effects' or 'lumetri'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the result shape (id, label, params) and the intended two-step discover-then-execute workflow with run_command. It stops short of saying whether all 650+ entries can come back at once or how results are bounded.

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?

Two tight sentences, zero filler. The scale and identity of the resource lead, and the routing instruction follows immediately.

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?

With no output schema, the description correctly compensates by naming the returned fields and the downstream execution tool. For a one-parameter search tool, an agent has everything needed to call it and act on the result.

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

Parameters3/5

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

Schema coverage is 100% and the single filter parameter already documents itself as a substring with examples ('effects', 'lumetri'). The description's parenthetical refers to returned fields, not the input, so it adds no meaning about the filter beyond the schema — baseline 3.

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?

Specific verb (Search) plus resource (FilmCraft's 650+ engine commands) plus the shape of each record (id, label, params). It also distinguishes itself from the many dedicated siblings by framing itself as the fallback discovery surface paired with run_command.

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 selection rule: use this plus run_command for anything that lacks a dedicated tool, with concrete domains named (effects, color, audio, captions, keyframes). It does not explicitly say when NOT to use it or how it relates to run_batch, which keeps it short of a 5.

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