Skip to main content
Glama
Sign In
animate-mcp

animate-mcp

by gekkyo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apply_scripts

Apply edited Timeline scripts from an export_scripts directory back to Adobe Animate scenes and library symbols, deleting frame scripts for empty files and preserving frames changed since export.

Instructions

Apply edited Timeline scripts from an export_scripts directory back to the Animate document (scenes and library symbols). Empty file deletes the frame script. Frames changed in Animate since Export are not overwritten. Does not save the .fla.

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": {
      "dir": "<dir>"
    },
    "name": "apply_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYes
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and discloses important traits: empty files delete frame scripts, conflicting frames are skipped, and the .fla is not saved. It does not cover permissions, return values, or partial-failure behavior, but the core mutation semantics are unusually well disclosed.

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?

Four short sentences, front-loaded with the main action and followed by the most important edge cases. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The behavioral description is strong for a mutation tool with no annotations or output schema, but the parameters remain almost entirely undocumented. An agent can understand what the tool does, yet cannot confidently determine what the document parameter should contain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters. It implies that dir points to an export_scripts directory, but it never explains the document parameter or the expected path format, leaving most parameter meaning undocumented.

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?

The description states a specific verb and resource: applying edited Timeline scripts from an export_scripts directory back to the Animate document. It also scopes the target to scenes and library symbols, which distinguishes it from the sibling export_scripts and edit_timeline tools.

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?

The workflow context is clear: this is for applying scripts that were previously exported and edited. The description also states that frames changed in Animate since export are not overwritten and that the .fla is not saved, but it does not explicitly name when to use a sibling tool instead.

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