Skip to main content
Glama

delete_sequence

Remove sequences from Adobe Premiere Pro projects to manage project structure and reduce clutter.

Instructions

Deletes a sequence from the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequenceIdYesThe ID of the sequence to delete

Implementation Reference

  • Registration of the delete_sequence tool in the executeTool dispatcher switch statement, calling the handler method.
    case 'delete_sequence':
      return await this.deleteSequence(args.sequenceId);
  • Input schema definition for the delete_sequence tool within getAvailableTools(), specifying the required sequenceId parameter.
    {
      name: 'delete_sequence',
      description: 'Deletes a sequence from the project.',
      inputSchema: z.object({
        sequenceId: z.string().describe('The ID of the sequence to delete')
      })
    },
  • The core handler implementation for delete_sequence, which constructs and executes an ExtendScript via the PremiereProBridge to locate and delete the sequence by its ID.
    private async deleteSequence(sequenceId: string): Promise<any> {
      const script = `
        try {
          var sequence = app.project.getSequenceByID("${sequenceId}");
          if (!sequence) {
            JSON.stringify({
              success: false,
              error: "Sequence not found"
            });
            return;
          }
          
          var sequenceName = sequence.name;
          app.project.deleteSequence(sequence);
          
          JSON.stringify({
            success: true,
            message: "Sequence deleted successfully",
            deletedSequenceId: "${sequenceId}",
            deletedSequenceName: sequenceName
          });
        } catch (e) {
          JSON.stringify({
            success: false,
            error: e.toString()
          });
        }
      `;
      
      return await this.bridge.executeScript(script);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is a deletion, implying it's destructive, but doesn't clarify if it's permanent, requires specific permissions, or has side effects (e.g., affecting linked media). This leaves significant gaps in understanding the tool's behavior.

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 no wasted words, making it highly efficient and front-loaded. Every word contributes to conveying the core purpose without unnecessary elaboration.

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 destructive nature, no annotations, and no output schema, the description is inadequate. It lacks critical details like confirmation requirements, error handling, or what happens post-deletion, making it incomplete 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?

The input schema has 100% description coverage, with 'sequenceId' clearly documented. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Deletes') and the resource ('a sequence from the project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'duplicate_sequence' or 'create_sequence' in terms of scope or constraints, which prevents a perfect score.

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, such as whether deletion is irreversible or if there are prerequisites like checking dependencies first. It also doesn't mention sibling tools like 'list_sequences' for reference, leaving usage context vague.

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