Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

prepare_export

Read-only

Set the loop/export range, open Live's Export Audio/Video dialog, and return render steps to export audio into the listen folder for listen_latest or match_reference.

Instructions

Set the loop/export range and open Live's Export Audio/Video dialog (Live's API has no export call), then return the steps to render into the listen folder for listen_latest / match_reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_beatNo
open_dialogNo
length_beatsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior2/5

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

The description does add genuine behavioral insight beyond the annotations: Live's API has no export call, so the tool can only open the dialog and hand back render steps. However, that same text reveals state changes (setting the loop/export range, opening a modal dialog) that conflict with readOnlyHint=true, so the behavioral profile presented is at odds with the declared annotations.

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?

One dense sentence, front-loaded with the action and parenthetically explaining the API constraint, with no filler. The nested clause about listen_latest / match_reference makes it slightly harder to parse but nothing is redundant.

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?

An output schema exists, so return values need not be spelled out, and the description usefully notes that the returned payload is render steps. What is missing is the behavior when open_dialog is false, the interaction model (a modal blocks the host until the user acts), and any confirmation of what the listen folder is.

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%, so all three parameters (start_beat, length_beats, open_dialog) rely on the description for meaning. The description only vaguely gestures at a 'loop/export range' and never mentions the open_dialog=false path, the beat units, or the null defaults, leaving most parameter meaning undocumented.

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 names a specific verb and resource: it sets the loop/export range and opens Live's Export Audio/Video dialog, then returns render steps. That is clearly distinct from siblings such as listen_latest and match_reference, which it names as downstream consumers. It falls short of 5 only because the split between 'range setting' and 'dialog opening' plus the returned steps is packed into one clause rather than delineated.

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

Usage Guidelines3/5

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

It situates the tool in a workflow (render into the listen folder for listen_latest / match_reference), which implies when to reach for it. But there is no explicit when-to-use or when-not statement, no mention of prerequisites (an active Live window, a modal dialog the user must complete), and no alternative named for exporting without the GUI.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools