Skip to main content
Glama
hetpatel-11

MCP Adobe Premiere Pro

by hetpatel-11
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

remove_effect

Remove specific effects from video clips in Adobe Premiere Pro to clean up edits or revert changes.

Instructions

Removes an effect from a clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIdYesThe ID of the clip
effectNameYesThe name of the effect to remove

Implementation Reference

  • src/tools/index.ts:1234-1280 (handler)
    The primary handler function for the 'remove_effect' tool. It constructs an ExtendScript that finds the clip by ID, iterates through its effects to find the matching effect name, removes it, and returns success/error status via the PremiereProBridge.
    private async removeEffect(clipId: string, effectName: string): Promise<any> {
  const script = `
    try {
      var clip = app.project.getClipByID("${clipId}");
      if (!clip) {
        JSON.stringify({
          success: false,
          error: "Clip not found"
        });
        return;
      }
      
      var effects = clip.getEffects();
      var removed = false;
      
      for (var i = 0; i < effects.length; i++) {
        if (effects[i].displayName === "${effectName}") {
          clip.removeEffect(effects[i]);
          removed = true;
          break;
        }
      }
      
      if (!removed) {
        JSON.stringify({
          success: false,
          error: "Effect not found on clip"
        });
        return;
      }
      
      JSON.stringify({
        success: true,
        message: "Effect removed successfully",
        clipId: "${clipId}",
        effectName: "${effectName}"
      });
    } catch (e) {
      JSON.stringify({
        success: false,
        error: e.toString()
      });
    }
  `;
  
  return await this.bridge.executeScript(script);
}
  • src/tools/index.ts:200-207 (registration)
    The 'remove_effect' tool is registered in the getAvailableTools() method, defining its name, description, and Zod input schema for validation.
    {
  name: 'remove_effect',
  description: 'Removes an effect from a clip.',
  inputSchema: z.object({
    clipId: z.string().describe('The ID of the clip'),
    effectName: z.string().describe('The name of the effect to remove')
  })
},
  • src/tools/index.ts:477-478 (registration)
    In the executeTool method's switch statement, the 'remove_effect' case dispatches to the removeEffect handler with parsed arguments.
      return await this.removeEffect(args.clipId, args.effectName);
case 'add_transition':
  • src/tools/index.ts:203-206 (schema)
    Zod schema definition for 'remove_effect' tool inputs: clipId (string) and effectName (string).
    inputSchema: z.object({
  clipId: z.string().describe('The ID of the clip'),
  effectName: z.string().describe('The name of the effect to remove')
})

Tool Definition Quality

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 the full burden of behavioral disclosure. It states the action ('Removes') but lacks critical details: whether this is destructive (permanently deletes the effect), requires specific permissions, has side effects (e.g., alters clip duration), or provides confirmation of removal. 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, direct sentence with zero wasted words. It front-loads the core action ('Removes') and target, making it easy to parse quickly. Every word earns its place, and there's no unnecessary elaboration or redundancy.

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 complexity of a mutation tool (removing effects) with no annotations and no output schema, the description is incomplete. It lacks information on behavior (e.g., success/failure responses, error conditions), side effects, and usage context. While the schema covers parameters, the overall tool understanding remains insufficient for reliable agent invocation.

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 parameter descriptions ('clipId' and 'effectName'), so the schema does the heavy lifting. The description adds no additional semantic context beyond implying these parameters are needed. It doesn't explain format expectations (e.g., effectName must match exactly) or relationships between parameters, resulting in a baseline score.

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 ('Removes') and the target ('an effect from a clip'), making the purpose immediately understandable. It distinguishes itself from siblings like 'apply_effect' by focusing on removal rather than application. However, it doesn't specify what constitutes an 'effect' (e.g., visual filter, audio effect) or the clip context (e.g., video editing), leaving some ambiguity.

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., the clip must have an effect applied), exclusions (e.g., cannot remove built-in effects), or related tools like 'apply_effect' for adding effects. Without such context, an agent might misuse it or overlook necessary steps.

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