Skip to main content
Glama

fusion_tool_add

Adds a Fusion tool by registry ID to a clip's comp, with options to insert it in the node chain and set input values.

Instructions

Add a Fusion tool (by registry ID) to a clip's comp. Common IDs: TextPlus, Transform, Merge, Background, Blur, ColorCorrector, BrightnessContrast, Glow, SoftGlow, FilmGrain, Rectangle, Ellipse, Polygon, BSpline, Tracker, PlanarTracker, CornerPositioner, DeltaKeyer, UltraKeyer, Shadow, DirectionalBlur, LensDistort, Vignette (via ofx), Text3D, Shape3D, Renderer3D, pRender/pEmitter (particles), sRectangle/sRender (shapes). insert=true wires it into the main chain: [after or the tool feeding MediaOut] → new → MediaOut. Generators (Background, TextPlus, shapes) are merged over the chain with a new Merge. inputs sets values.

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": {
      "tool_type": "<tool_type>"
    },
    "name": "fusion_tool_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
clipNocurrent
compNo
nameNo
afterNo
inputsNo
insertNo
tool_typeYes
create_compNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: how insert=true rewires the chain, that generators are merged over the chain with a new Merge, and that inputs sets values. It is silent on permissions, whether an existing comp is modified destructively, what create_comp does, and what is returned.

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?

The core action and the key default (insert=true) are front-loaded, and every sentence adds information. The long inline ID list is dense and unstructured, making the block harder to scan than a bulleted breakdown would be, but it is not padding.

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?

For a 10-parameter mutation tool with zero annotation coverage and no output schema, the description covers the operationally important parts (tool selection, chain insertion, generator merging) but leaves half the parameters and all return behavior unexplained. Adequate to attempt a call, not complete enough to call confidently.

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 0% across 10 parameters, so the description must compensate, and it does so for tool_type (a genuinely useful ID catalog), insert, after, and inputs. The remaining parameters, x, y, clip, comp, name, and create_comp, receive no explanation in either the schema or the description, leaving roughly half the surface ambiguous.

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 opens with a specific verb and resource: 'Add a Fusion tool (by registry ID) to a clip's comp,' and enumerates concrete tool IDs, so the agent knows exactly what gets created. It does not, however, distinguish itself from plausible siblings like generator_add, title_add, or transition_add, which an agent could easily confuse with Fusion tool insertion.

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

Usage Guidelines3/5

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

Usage is only implied: the tool list and the description of insert=true make the intent inferable, but there is no explicit 'use this when… / use X instead when…' statement. The agent is left to guess whether a Background generator should be added via generator_add or via this tool.

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