Skip to main content
Glama

get_browser_tree

Retrieve a hierarchical tree of browser categories from Ableton Live to organize instruments, sounds, effects, and drum kits for music production.

Instructions

Get a hierarchical tree of browser categories from Ableton.

Parameters:

  • category_type: 'all', 'instruments', 'sounds', 'drums', 'audio_effects', 'midi_effects'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_typeNoall

Implementation Reference

  • The actual implementation of the get_browser_tree logic within the Ableton Remote Script. It interacts with the Live application's browser object.
    def get_browser_tree(self, category_type="all"):
        """
        Get a simplified tree of browser categories.
        
        Args:
            category_type: Type of categories to get ('all', 'instruments', 'sounds', etc.)
            
        Returns:
            Dictionary with the browser tree structure
        """
        try:
            # Access the application's browser instance instead of creating a new one
            app = self.application()
            if not app:
                raise RuntimeError("Could not access Live application")
                
            # Check if browser is available
            if not hasattr(app, 'browser') or app.browser is None:
                raise RuntimeError("Browser is not available in the Live application")
            
            # Log available browser attributes to help diagnose issues
            browser_attrs = [attr for attr in dir(app.browser) if not attr.startswith('_')]
            self.log_message("Available browser attributes: {0}".format(browser_attrs))
            
            result = {
                "type": category_type,
                "categories": [],
                "available_categories": browser_attrs
            }
            
            # Helper function to process a browser item and its children
            def process_item(item, depth=0):
                if not item:
                    return None
                
                result = {
                    "name": item.name if hasattr(item, 'name') else "Unknown",
                    "is_folder": hasattr(item, 'children') and bool(item.children),
                    "is_device": hasattr(item, 'is_device') and item.is_device,
                    "is_loadable": hasattr(item, 'is_loadable') and item.is_loadable,
                    "uri": item.uri if hasattr(item, 'uri') else None,
                    "children": []
                }
                
                
                return result
  • The MCP tool definition that acts as a bridge, calling the underlying remote script method via `_run`.
    def get_browser_tree(ctx: Context, category_type: str = "all") -> str:
        """
        Get a hierarchical tree of browser categories from Ableton.
    
        Parameters:
        - category_type: 'all', 'instruments', 'sounds', 'drums', 'audio_effects', 'midi_effects'
        """
        try:
            result = _run("get_browser_tree", {"category_type": category_type})
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 it 'Get[s] a hierarchical tree,' implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, error handling, or what the tree structure looks like (e.g., JSON format, depth). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by a parameter section. There's minimal waste, though it could be slightly more structured (e.g., bullet points for the enum list). Every sentence adds value, making it efficient.

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 moderate complexity (1 parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the purpose and parameter semantics well, but lacks behavioral details (e.g., return format, error cases) and usage guidelines. Without an output schema, it should ideally hint at the return value, but this isn't critical for a basic read operation.

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 description adds substantial meaning beyond the input schema. Schema description coverage is 0%, and the schema only lists 'category_type' with a default and title. The description explicitly lists the enum values ('all', 'instruments', etc.), which are not in the schema, providing crucial semantic context for the single parameter. Since there's only one parameter, this compensation is effective.

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 tool's purpose: 'Get a hierarchical tree of browser categories from Ableton.' It specifies the verb ('Get'), resource ('hierarchical tree of browser categories'), and source ('from Ableton'). However, it doesn't explicitly differentiate from its sibling 'get_browser_items_at_path', which likely retrieves items rather than categories, so it misses full sibling distinction.

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 sibling tools like 'get_browser_items_at_path' or explain the context for fetching categories versus items. Usage is implied only by the tool name and description, with no explicit when/when-not instructions.

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/FreeRiverHouse/ableton-flow'

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