Skip to main content
Glama

Filmagic

Make a launch video from a website

create_video
Read-only

Start a Filmagic video from a product website. Returns a filmagic.app link: opening it reads the site and builds the video in the browser, ready to preview, edit and export. Without a template, Filmagic writes a custom cut for the product; with one, it fills that template.

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": {
      "url": "<url>"
    },
    "name": "create_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe product website, e.g. https://yourproduct.com
templateNoOptional template id, e.g. "xstyle", "beam" or "whatsnew"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the non-obvious behavioral fact that the tool returns a link whose opening triggers browser-side reading of the site and video construction, which is exactly the kind of context an agent cannot get from the schema. It stops short of covering auth requirements, failure modes, or how long the link remains valid, so a 4 rather than 5.

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 short sentences, front-loaded with the action and the return value, then the mode distinction. Nothing is padded and no sentence merely restates the title.

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 two-parameter tool with no output schema, the description covers the action, the return artifact, and the parameter-dependent behavior adequately. The remaining gap is minor: it never mentions how to obtain valid template ids or any prerequisite/auth context.

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%, so the baseline is 3, but the description genuinely adds meaning: omitting the template yields a custom cut written for the product, while supplying one fills that template instead. That behavioral distinction between the two parameters is not stated in the schema.

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?

It names a specific verb and resource ('Start a Filmagic video from a product website') and immediately clarifies what is actually produced: a filmagic.app link rather than a finished file. The two operating modes (custom cut vs. template fill) further pin down what the call does, and the unrelated siblings (get_pricing, list_templates) need no differentiation.

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 context is implied by 'from a product website', and the template/no-template sentence effectively guides how to choose that parameter. However, there is no explicit when-to-use vs. when-not framing and no pointer to list_templates for discovering template ids, even though that sibling exists.

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