Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

save_expression_preset

Store After Effects expressions as reusable presets with customizable parameters for efficient animation workflows.

Instructions

Save an expression as a preset for reuse

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": {
      "name": "<name>",
      "expression": "<expression>"
    },
    "name": "save_expression_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the preset
categoryNoCategory for organizing presetsCustom
expressionYesThe expression code
descriptionNoDescription of what the expression does
parametersNoParameters that can be customized in the expression

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'save' implies a write operation but doesn't disclose behavioral traits like whether it overwrites existing presets, requires specific permissions, or returns confirmation. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's purpose, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior (e.g., overwrite rules), error conditions, or return values, leaving gaps in understanding how the tool operates in practice.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond implying an 'expression' is saved, which is already clear from parameter names. Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly states the action ('save') and resource ('expression as a preset'), specifying it's for reuse. However, it doesn't differentiate from siblings like 'apply_expression_preset' or 'set_expression', which handle different aspects of expression management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'apply_expression_preset' or 'set_expression'. The description lacks context about prerequisites, such as whether an expression must be active or valid, or when saving is appropriate.

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