Skip to main content
Glama

get_selection_info

Retrieve details about selected clips or time ranges in Adobe Premiere Pro for automation and AI integration workflows.

Instructions

Get information about currently selected clips or time range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the tool logic by fetching selection data from the local HTTP API endpoint at http://localhost:3001/api/selection, processes the response, handles errors, and returns formatted content about selected clips or time range.
    async getSelectionInfo() {
      try {
        const response = await fetch('http://localhost:3001/api/selection');
        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}`,
              },
            ],
          };
        }
    
        if (data.selection_type === 'none') {
          return {
            content: [
              {
                type: 'text',
                text: `🎯 **Selection Info**\n\nNo clips or time range currently selected.`,
              },
            ],
          };
        }
    
        const selectedClips = data.selected_clips.map(clip => 
          `• **${clip.clip_name}** (${clip.track_type}${clip.track_number})`
        ).join('\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎯 **Selection Info**\n\n**Type:** ${data.selection_type}\n**Selected Clips:**\n${selectedClips}\n\n**Time Range:** ${data.selection_in} → ${data.selection_out}\n**Duration:** ${data.selection_duration}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get selection info**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • mcp-server.js:249-250 (registration)
    In the tool call request handler switch statement, routes calls to the getSelectionInfo handler method.
    case 'get_selection_info':
      return await this.getSelectionInfo();
  • mcp-server.js:119-127 (registration)
    Registers the tool in the list of available tools returned by ListToolsRequestHandler, including name, description, and empty input schema.
    {
      name: "get_selection_info",
      description: "Get information about currently selected clips or time range",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Defines the input schema for the tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
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. While it implies a read-only operation ('Get information'), it lacks details on permissions, rate limits, error conditions, or what specific information is returned. This is inadequate for a tool with zero annotation coverage.

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, clear sentence with no wasted words. It front-loads the core purpose efficiently, making it easy to parse and understand immediately.

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 lack of annotations and output schema, the description is insufficient. It doesn't explain what 'information' includes (e.g., metadata, duration, format), how 'currently selected' is determined, or the return format. For a tool in a context with many similar siblings, more detail is needed to guide proper use.

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 tool has zero parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description correctly omits parameter details, earning a high baseline score for not adding 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 verb ('Get') and resource ('information about currently selected clips or time range'), making the tool's purpose understandable. However, it doesn't explicitly differentiate this tool from similar sibling tools like 'get_active_sequence_info' or 'get_timeline_clips', 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. With multiple sibling tools that retrieve information (e.g., 'get_active_sequence_info', 'get_timeline_clips'), there's no indication of context, prerequisites, or exclusions for this specific tool.

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