Skip to main content
Glama

list_all_sequences

Retrieve all sequences in your Adobe Premiere Pro project with basic information for project management and workflow automation.

Instructions

List all sequences in the current project with basic info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main execution logic for list_all_sequences tool: fetches sequence data from HTTP API and returns formatted list.
    async listAllSequences() {
      try {
        const response = await fetch('http://localhost:3001/api/sequences');
        if (!response.ok) throw new Error(`HTTP ${response.status}: ${response.statusText}`);
        
        const data = await response.json();
        
        if (data.error) {
          return {
            content: [
              {
                type: 'text',
                text: `⚠️  ${data.error}`,
              },
            ],
          };
        }
    
        const sequenceList = data.sequences.map(seq => 
          `• **${seq.name}** (${seq.duration}) - ${seq.resolution} @ ${seq.frame_rate}fps - ${seq.clip_count} clips ${seq.is_active ? '✅ ACTIVE' : ''}`
        ).join('\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎬 **All Sequences (${data.total_sequences})**\n\n${sequenceList}\n\n**Active Sequence:** ${data.active_sequence}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to list sequences**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Tool schema definition including name, description, and empty input schema, used in ListTools response.
    {
      name: "list_all_sequences",
      description: "List all sequences in the current project with basic info",
      inputSchema: {
        type: "object", 
        properties: {},
        required: []
      }
    },
  • mcp-server.js:228-229 (registration)
    Registration in the tool dispatch switch statement within CallToolRequestSchema handler.
    case 'list_all_sequences':
      return await this.listAllSequences();
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 mentions 'basic info' but doesn't specify what that includes (e.g., sequence names, IDs, durations), whether the list is paginated, sorted, or filtered, or any performance considerations. For a read operation with zero annotation coverage, 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, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place, adhering to best practices for conciseness.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on output format, behavioral traits, and usage context relative to siblings. For a list operation in a media project environment, more guidance on what 'basic info' entails would enhance completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description appropriately adds no parameter details, as there are none to explain. This meets the baseline of 4 for tools with zero parameters, as it avoids unnecessary information.

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 ('List all sequences') and resource ('in the current project'), with the scope of 'basic info'. It distinguishes from siblings like 'get_sequence_details' (which likely provides detailed info) and 'get_active_sequence_info' (which focuses on active sequences). However, it doesn't explicitly contrast with these siblings, keeping it at 4 instead of 5.

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 minimal guidance, stating only the context ('in the current project'). It offers no explicit when-to-use rules, alternatives (e.g., vs. 'get_sequence_details' for more details), or exclusions. Without this, the agent must infer usage from the tool name and sibling context alone.

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/jordanl61/premiere-pro-mcp-server'

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