Skip to main content
Glama

List Filmagic templates

list_templates
Read-only

List Filmagic video and social post templates with what each is for, its category and lengths. Filter by category (Launch, Posts, Story, Product, Mockup, Demo, Social) or a search word.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 25)
queryNoA word to match in the name or use, e.g. "AI", "app", "carousel"
categoryNoLaunch, Posts, Story, Product, Mockup, Demo or Social

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output context ('what each is for, its category and lengths'), but does not mention the default page size of 25, truncation, or ordering — behaviors a listing tool call should disclose.

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?

A single dense sentence with the resource and returned fields front-loaded, followed by the filtering options. There is no filler and nothing redundant.

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?

For a simple read-only list tool with three optional, fully documented parameters, the description is nearly sufficient, covering what is returned and how to filter. It stops short only on result-size and ordering behavior, which matters slightly more because there is no output schema.

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%, so all three parameters are already documented in the schema, including the category list and query examples. The description repeats that same category list and search-word concept without adding syntax, matching behavior, or default behavior beyond the schema's 'default 25'.

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 (List) plus the resource (Filmagic video and social post templates) and even what each record contains (purpose, category, lengths). The resource is plainly distinct from the sibling create_video and get_pricing tools, so an agent can select it without ambiguity.

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?

The description explains how to narrow results ('Filter by category ... or a search word') but never states when to choose this tool over an alternative or when not to use it. Usage is implied (browse/discover templates) rather than taught.

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