Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_list_export_presets

List available FilmCraft export presets—built-in and user-defined—with name, category, and format, with optional text-query filtering.

Instructions

List all available filmCraft export presets (built-in and user-defined) with name, category, and format.

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": "fc_list_export_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional text filter on preset name or category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that both built-in and user-defined presets are returned with name, category, and format, which reveals the read shape, but it says nothing about ordering, pagination, or permissions — minor for a plain list operation, but unstated.

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?

One well-formed sentence with the resource and scope front-loaded and no filler. The parenthetical and returned-field enumeration are earned information rather than 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?

For a one-optional-parameter read tool with no annotations and no output schema, the description covers what the tool returns (name, category, format) and the preset scope. Nothing essential to calling it correctly is missing.

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% with a single optional 'query' parameter fully documented in the schema. The description adds no filtering semantics of its own and its 'List all available' phrasing arguably understates that the result can be filtered, so it neither compensates nor detracts significantly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('List all available filmCraft export presets') and adds scope detail ('built-in and user-defined') plus the returned fields. It implicitly separates itself from fc_list_commands and fc_export by naming the resource 'presets', though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the name and the word 'List'; the description never states when to call this versus fc_export or fc_describe, nor does it mention that presets returned here feed into an export. An agent can infer the purpose, but no guidance is spelled out.

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

Deploy Server

Other Tools