Skip to main content
Glama

get_clip_info_by_id

Retrieve detailed clip information from Ableton Live by specifying a clip ID. This tool supports real-time interaction with Ableton Copilot MCP for efficient clip operations and workflow management.

Instructions

Get clip info by clip id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clip_idYes

Implementation Reference

  • Registration of the tool 'get_clip_properties' via @tool decorator, which matches the function getClipInfoById for getting clip info by ID.
    @tool({
        name: 'get_clip_properties',
        description: 'Get clip properties by clip id. To get specific properties, set the corresponding property name to true in the properties parameter.',
        paramsSchema: {
            clip_id: z.string(),
            properties: ClipGettableProp,
        }
    })
  • Handler function that executes the tool logic: retrieves the clip by ID and gets the specified properties.
    async getClipInfoById({ clip_id, properties }: { clip_id: string, properties: z.infer<typeof ClipGettableProp> }) {
        const clip = getClipById(clip_id)
        return await getClipProps(clip, properties)
    }
  • Zod schema definition for ClipGettableProp used in the tool parameters for specifying which clip properties to retrieve.
    export const ClipGettableProp = createZodSchema<ClipGettablePropType>({
        available_warp_modes: z.boolean().optional(),
        color: z.boolean().optional(),
        color_index: z.boolean().optional(),
        end_marker: z.boolean().optional(),
        end_time: z.boolean().optional(),
        file_path: z.boolean().optional(),
        gain: z.boolean().optional(),
        gain_display_string: z.boolean().optional(),
        has_envelopes: z.boolean().optional(),
        is_arrangement_clip: z.boolean().optional(),
        is_audio_clip: z.boolean().optional(),
        is_midi_clip: z.boolean().optional(),
        is_overdubbing: z.boolean().optional(),
        is_playing: z.boolean().optional(),
        is_recording: z.boolean().optional(),
        is_triggered: z.boolean().optional(),
        launch_mode: z.boolean().optional(),
        launch_quantization: z.boolean().optional(),
        length: z.boolean().optional(),
        loop_end: z.boolean().optional(),
        loop_start: z.boolean().optional(),
        looping: z.boolean().optional(),
        muted: z.boolean().optional(),
        name: z.boolean().optional(),
        pitch_coarse: z.boolean().optional(),
        pitch_fine: z.boolean().optional(),
        playing_position: z.boolean().optional(),
        position: z.boolean().optional(),
        ram_mode: z.boolean().optional(),
        sample_length: z.boolean().optional(),
        selected_notes: z.boolean().optional(),
        signature_denominator: z.boolean().optional(),
        signature_numerator: z.boolean().optional(),
        start_marker: z.boolean().optional(),
        start_time: z.boolean().optional(),
        velocity_amount: z.boolean().optional(),
        warp_mode: z.boolean().optional(),
        warp_markers: z.boolean().optional(),
        warping: z.boolean().optional(),
        will_record_on_start: z.boolean().optional()
    }).extend({
        notes: z.boolean().optional(),
        selected_notes: z.boolean().optional(),
    })
  • Uses helper functions getClipById and getClipProps to implement the logic.
    const clip = getClipById(clip_id)
    return await getClipProps(clip, properties)
  • src/main.ts:41-41 (registration)
    Class-level registration of ClipTools in the MCP server startup.
    tools: [BrowserTools, ClipTools, DeviceTools, HistoryTools, SongTools, TrackTools, ExtraTools, ApplicationTools]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions, rate limits, response format, or error handling. This is inadequate for a tool with potential read operations and no output schema.

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 concise with a single sentence, but it's under-specified rather than efficiently informative. It front-loads the core action but lacks necessary details, making it borderline between brevity and insufficiency.

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 complexity (1 parameter, no annotations, no output schema), the description is incomplete. It doesn't explain what 'clip info' includes, how to interpret results, or handle errors, leaving significant gaps for an AI agent to use the tool effectively.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions 'clip id' without adding meaning beyond the schema's 'clip_id' parameter. It fails to explain what a clip ID is, its format, or examples, leaving the parameter semantics unclear.

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

Purpose3/5

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

The description 'Get clip info by clip id' clearly states the verb ('Get') and resource ('clip info'), but it's vague about what 'clip info' entails. It doesn't differentiate from siblings like 'get_detail_clip' or 'get_clips_by_track_id', leaving the scope ambiguous.

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 on when to use this tool versus alternatives such as 'get_detail_clip' or 'get_clips_by_track_id'. The description implies usage by clip ID but offers no context on prerequisites, exclusions, or comparisons to sibling tools.

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

Related 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/xiaolaa2/ableton-copilot-mcp'

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