Skip to main content
Glama
Sign In

Creator MCP

by com.lottiefiles
OverviewDiscussionsAdmin

Save to the LottieFiles workspace

creator_save_to_workspace

Save to the caller's LottieFiles workspace; give the user the returned creatorUrl, which opens the file in LottieFiles Creator. Default: exports the focused composition as a dotLottie; file uploads a ready Lottie JSON output file instead. fileId saves a new version of that file; omit it for a new file in Drafts. Errors: empty_document, no_focused_composition (creator.focusOn first), unsupported_file, not_found, expired, file_not_found, payload_too_large.

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

Input Schema

NameRequiredDescriptionDefault
fileNoA ready Lottie JSON output file (creator.export(file, "lottie")) to upload instead of exporting the document.
nameNoTitle, 1-100 characters (default: the file's title with fileId, else the composition's name or output file's stem).
fileIdNoWorkspace file to save a new version of; omit for a new file in Drafts.
documentIdNoDocument to save (default "default").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, open-world; the description adds real behavior beyond that: the two write paths (new Drafts file vs new version of an existing file), the side effect of the user-facing creatorUrl, and a concrete enumerated error set. It does not say whether version-saving overwrites prior content or what permissions/scopes are needed.

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 purpose then behavior then errors, and nearly every clause carries non-redundant information. It is packed into semicolon-delimited fragments, which is dense and slightly harder to scan than a short structured list, but nothing is wasted.

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 4-optional-param write tool with an output schema present, the description covers the mode selection, default behavior, follow-up action, and failure modes well enough to call it correctly. Missing only permission/auth expectations and conflict behavior on name or version collisions.

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 baseline is 3, but the description earns a bump by explaining parameter interaction rather than repeating definitions: `file` substitutes for the default export, `fileId` selects version-save mode, and omitting it places a new file in Drafts. `name` and `documentId` are left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource (save a file into the caller's LottieFiles workspace) and immediately distinguishes the three modes: default composition export, `file` upload, and `fileId` version update. It does not explicitly name the inverse sibling (creator_load_from_workspace), but the intent is unambiguous.

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 clear operating guidance: default exports the focused composition, pass `file` when you already have Lottie JSON, pass `fileId` to version an existing file, omit it for Drafts. It also prescribes the follow-up action (hand the user the returned creatorUrl) and routes the no_focused_composition error to creator.focusOn. No explicit when-not-to-use-this-tool-vs-siblings statement.

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