Skip to main content
Glama
AE Motion MCP
by dha-aa

Edit Effect

edit_effect
Destructive

Remove, enable, disable, or configure an effect on a layer by its 1-based index, including updating effect parameters after validation.

Instructions

Remove, enable or disable an effect on a layer by its 1-based index (see get_layer for the list), or set: change params as in apply_effect (all checked first).

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": {
      "layer_id": "<layer_id>",
      "effect_index": "<effect_index>",
      "action": "<action>"
    },
    "name": "edit_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNo
layer_idYes
effect_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.25.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "remove",
      -  "enable",
      -  "disable"
      -]New value: +[
      +  "remove",
      +  "enable",
      +  "disable",
      +  "set"
      +]
    • addedInput schema / properties / params
      Added value: +{
      +  "additionalProperties": {
      +    "anyOf": [
      +      {
      +        "type": [
      +          "number",
      +          "string",
      +          "boolean"
      +        ]
      +      },
      +      {
      +        "items": {
      +          "type": "number"
      +        },
      +        "type": "array"
      +      }
      +    ]
      +  },
      +  "type": "object"
      +}
  2. First observedv2.22.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is covered. The description adds one genuinely useful behavior — parameters are validated first ("all checked first") — but says nothing about what removal destroys (keyframed parameters, animation data) or whether enable/disable are reversible no-op-style toggles.

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?

A single dense sentence that front-loads the three simple actions before the more complex set path. No filler, though the colon-and-parenthetical stacking makes it harder to parse than separate clauses would be.

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 destructive four-parameter mutation with no output schema, the definition supplies the index convention, the action vocabulary, the lookup tool and the validation-before-write guarantee. Missing details about what removal cascades to are nice-to-have rather than blocking.

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?

With schema description coverage at 0%, the description must carry parameter meaning, and it does cover effect_index (1-based, with a pointer to get_layer) and params (delegated to apply_effect). layer_id and the nested params value types remain undocumented, so half the surface still relies on inference.

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?

Names a specific verb set (remove/enable/disable/set) applied to an effect on a layer, and the action enum is mirrored verbatim so the agent can map intent to enum value. The closing clause "or set: change params as in apply_effect" is slightly elliptical but still identifies the fourth operation and points at the analogous tool.

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?

Explicitly routes to get_layer for retrieving the effect index and to apply_effect for parameter semantics, which is exactly the context needed before calling. It stops short of saying when to enable/disable versus remove, or when to prefer apply_effect over action=set, but the alternatives it does name are the right ones.

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