Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_browser_item_metadata

Read-onlyIdempotent

Search saved private tags and favorites to locate Ableton Live browser items or local_splice samples by root, tags, favorite, and limit.

Instructions

Search saved private tags and favorites for Live browser items or local_splice samples. Results are not reverified against Live or the local filesystem and do not represent native collections.

Input Schema

NameRequiredDescriptionDefault
rootNoOptional browser root or local_splice filter.
tagsNoRequire all tags.
limitNo
favoriteNoOptional private favorite filter.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "items": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "limitation": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "items",
+      "limitation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changedv0.3.0
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / root / description
      Previous value: -"Optional browser root filter."New value: +"Optional browser root or local_splice filter."
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, closed-world operation. The description adds meaningful behavioral context: results are not reverified against Live or the filesystem and do not represent native collections, which prevents over-trusting the output.

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?

Two sentences, no filler, and the key scope plus the important caveat are front-loaded. Every sentence earns its place.

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

Completeness4/5

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

An output schema exists and the annotations cover the safety profile, so the description does not need to explain return values. It adequately covers scope and the unverified/non-native caveat, though it could more clearly relate to the sibling browser search tools.

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

Parameters3/5

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

Schema coverage is 75%, so most parameters are documented. The description's 'private tags and favorites' reinforces the tags and favorite parameters but adds no detail about root filtering or the limit parameter, leaving the schema to do the heavy lifting.

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: searching saved private tags and favorites for Live browser items or local_splice samples. It also distinguishes this from native collections, though it does not explicitly name the sibling search_browser_items tool as the alternative.

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?

Usage is implied by 'saved private tags and favorites' — the agent can infer this is for querying private metadata rather than the native browser. However, there is no explicit when-to-use versus search_browser_items, search_presets, or get_browser_item_metadata, and no exclusions.

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