Skip to main content
Glama

get_browser_items_at_path

Retrieve items from Ableton Live's browser at a specified path to access instruments, samples, and effects for music production.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • MCP tool handler for get_browser_items_at_path. Connects to Ableton, sends the command with the given path, handles the result or specific errors, and returns JSON or formatted error message.
    @mcp.tool()
    def get_browser_items_at_path(ctx: Context, path: str) -> str:
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("get_browser_items_at_path", {"path": path})
            if "error" in result and "available_categories" in result:
                error = result.get("error", "")
                available_cats = result.get("available_categories", [])
                return (f"Error: {error}\n"
                       f"Available browser categories: {', '.join(available_cats)}")
            return json.dumps(result, indent=2)
        except Exception as e:
            error_msg = str(e)
            if "Browser is not available" in error_msg:
                logger.error(f"Browser is not available in Ableton: {error_msg}")
                return f"Error: The Ableton browser is not available. Make sure Ableton Live is fully loaded and try again."
            elif "Could not access Live application" in error_msg:
                logger.error(f"Could not access Live application: {error_msg}")
                return f"Error: Could not access the Ableton Live application. Make sure Ableton Live is running and the Remote Script is loaded."
            elif "Unknown or unavailable category" in error_msg:
                logger.error(f"Invalid browser category: {error_msg}")
                return f"Error: {error_msg}. Please check the available categories using get_browser_tree."
            elif "Path part" in error_msg and "not found" in error_msg:
                logger.error(f"Path not found: {error_msg}")
                return f"Error: {error_msg}. Please check the path and try again."
            else:
                logger.error(f"Error getting browser items at path: {error_msg}")
                return f"Error getting browser items at path: {error_msg}"
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/Milesy1/MCP-Ableton-API'

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