Skip to main content
Glama

apply_effect

Apply visual or audio effects to timeline clips in Adobe Premiere Pro. Specify clip ID, effect name, and parameters to enhance video editing workflows.

Instructions

Applies a visual or audio effect to a specific clip on the timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIdYesThe ID of the clip to apply the effect to
effectNameYesThe name of the effect to apply (e.g., "Gaussian Blur", "Lumetri Color")
parametersNoKey-value pairs for the effect's parameters

Implementation Reference

  • The core handler function for the 'apply_effect' tool. It generates an ExtendScript that finds the clip by ID, adds the specified effect, sets any provided parameters, and returns the result via the PremiereProBridge.
    private async applyEffect(clipId: string, effectName: string, parameters?: Record<string, any>): Promise<any> {
      const script = `
        try {
          var clip = app.project.getClipByID("${clipId}");
          if (!clip) {
            JSON.stringify({
              success: false,
              error: "Clip not found"
            });
            return;
          }
          
          var effect = clip.addEffect("${effectName}");
          if (!effect) {
            JSON.stringify({
              success: false,
              error: "Effect not found or could not be applied"
            });
            return;
          }
          
          ${parameters ? Object.entries(parameters).map(([key, value]) => 
            `try { if (effect.properties["${key}"]) effect.properties["${key}"].setValue(${JSON.stringify(value)}); } catch (e) { /* Parameter not found */ }`
          ).join('\n') : ''}
          
          JSON.stringify({
            success: true,
            message: "Effect applied successfully",
            clipId: "${clipId}",
            effectName: "${effectName}",
            effectId: effect.matchName,
            parametersApplied: ${parameters ? Object.keys(parameters).length : 0}
          });
        } catch (e) {
          JSON.stringify({
            success: false,
            error: e.toString()
          });
        }
      `;
      
      return await this.bridge.executeScript(script);
    }
  • Zod schema defining the input parameters for the apply_effect tool: clipId (required string), effectName (required string), parameters (optional record).
    inputSchema: z.object({
      clipId: z.string().describe('The ID of the clip to apply the effect to'),
      effectName: z.string().describe('The name of the effect to apply (e.g., "Gaussian Blur", "Lumetri Color")'),
      parameters: z.record(z.any()).optional().describe('Key-value pairs for the effect\'s parameters')
    })
  • Tool registration in the getAvailableTools() method's return array, including name, description, and schema.
      name: 'apply_effect',
      description: 'Applies a visual or audio effect to a specific clip on the timeline.',
      inputSchema: z.object({
        clipId: z.string().describe('The ID of the clip to apply the effect to'),
        effectName: z.string().describe('The name of the effect to apply (e.g., "Gaussian Blur", "Lumetri Color")'),
        parameters: z.record(z.any()).optional().describe('Key-value pairs for the effect\'s parameters')
      })
    },
  • Dispatch/registration in the executeTool switch statement that routes calls to the applyEffect handler.
    case 'apply_effect':
      return await this.applyEffect(args.clipId, args.effectName, args.parameters);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool applies effects but lacks details on permissions needed, whether it's destructive (e.g., overwrites existing effects), rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 that front-loads the core purpose without unnecessary details. It's appropriately sized for the tool's complexity, with zero wasted words, 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?

Given the tool's complexity (3 parameters, mutation operation) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error handling, or return values, which are crucial for safe and effective use by an AI agent.

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%, with clear descriptions for all parameters (clipId, effectName, parameters). The description adds no additional meaning beyond the schema, such as example effect names or parameter formats, so it meets the baseline of 3 where the 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 tool's purpose as 'Applies a visual or audio effect to a specific clip on the timeline,' specifying the action (apply), target (effect), and resource (clip). It distinguishes from siblings like 'remove_effect' or 'color_correct' by focusing on application rather than removal or specific effect types, though it doesn't explicitly contrast with all alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing clip or effect), exclusions (e.g., not for text overlays), or comparisons to siblings like 'apply_lut' or 'color_correct,' leaving usage context implied but unspecified.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hetpatel-11/Adobe_Premiere_Pro_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server