Skip to main content
Glama

get_project_bins

Retrieve the bin structure and organization of Adobe Premiere Pro projects to manage media assets and streamline editing workflows.

Instructions

Get project bin structure and organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches project bins data from the local API endpoint, processes the hierarchical bin structure, formats it with indentation and emojis, handles errors, and returns structured MCP content.
    async getProjectBins() {
      try {
        const response = await fetch('http://localhost:3001/api/project-bins');
        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 binsList = data.bins.map(bin => {
          const indent = bin.parent_bin ? '  ' : '';
          const subBins = bin.sub_bins.length > 0 ? ` (${bin.sub_bins.length} sub-bins)` : '';
          return `${indent}📁 **${bin.bin_name}** - ${bin.media_count} items${subBins} ${bin.color_label ? `🏷️ ${bin.color_label}` : ''}`;
        }).join('\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `📁 **Project Bins (${data.total_bins} total)**\n\n${binsList}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get project bins**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for the get_project_bins tool, which requires no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • mcp-server.js:101-109 (registration)
    Tool registration in ListToolsRequestHandler, defining name, description, and schema.
    {
      name: "get_project_bins",
      description: "Get project bin structure and organization",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:243-244 (registration)
    Handler dispatch in CallToolRequestHandler switch statement, routing 'get_project_bins' calls to the getProjectBins method.
    case 'get_project_bins':
      return await this.getProjectBins();
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read operation ('Get'), but doesn't disclose behavioral traits such as permissions needed, rate limits, or what 'structure and organization' entails in terms of return format or scope.

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 action and resource. It's appropriately sized with no 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is minimal but adequate for a simple read operation. However, without annotations or output details, it lacks completeness in explaining what 'structure and organization' means in practice, leaving gaps in understanding the tool's behavior.

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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description doesn't need to add parameter details, as there are none, and it appropriately focuses on the tool's purpose without redundant 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 the resource 'project bin structure and organization', making the purpose understandable. However, it doesn't differentiate from siblings like 'get_project_info' or 'get_timeline_structure', which might also provide organizational data.

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?

No guidance is provided about when to use this tool versus alternatives. With siblings like 'get_project_info' and 'get_timeline_structure' that might overlap, the description offers no context about specific use cases or exclusions.

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