Skip to main content
Glama
Sign In

Creator MCP

by com.lottiefiles
OverviewDiscussionsAdmin

Load a file from the LottieFiles workspace

creator_load_from_workspace
Destructive

Load a LottieFiles workspace file into the document by fileId. mode "replace" discards the document (content, files, output files) and commits the file as its next revision, with no confirmation; mode "add" adds its compositions beside the existing ones. Edit the result with creator_exec; creator_save_to_workspace with the same fileId saves a new version. Files created inside Creator return unsupported_file; also file_not_found, file_too_large, workspace_download_failed (retry).

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": {
      "fileId": "<fileId>",
      "mode": "<mode>"
    },
    "name": "creator_load_from_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes"replace": the document becomes the file. "add": the file's compositions are added beside the existing ones.
fileIdYesWorkspace file to load, from an earlier save or the user.
documentIdNoDocument to load into (default "default").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it spells out that "replace" discards content, files, and output files with no confirmation, which sharpens the destructiveHint=true declaration. It also documents concrete failure behaviors (unsupported_file for Creator-created files; workspace_download_failed is retryable), which the annotations cannot convey.

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?

Front-loaded with the core action and the mode distinction, then follow-up tools and error codes. It is dense and reads as a long run-on, but nearly every clause carries actionable information, so little is wasted.

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 destructive, open-world load tool with an output schema already covering return values, the description supplies the mutation semantics, follow-up workflow, and expected error codes. Nothing an agent needs to invoke it safely appears to be missing.

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 schema already defines all three parameters and the enum. The description still adds meaning by clarifying the consequence of "replace" (document, files, and output files are discarded and the file becomes the next revision), which is more specific than the schema's "the document becomes the file".

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 ("Load a LottieFiles workspace file into the document by fileId") and immediately distinguishes the two modes. It also names the sibling tools that operate on the result (creator_exec, creator_save_to_workspace), so an agent can place it in the workflow without opening other schemas.

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?

Explains what each mode does and points to creator_save_to_workspace with the same fileId for the save path, giving clear routing context. It stops short of explicit "prefer add when..." guidance, so the replace-vs-add decision is left partly to inference from the mode semantics.

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

All Creator MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources