Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_session_selection_tool

Set or clear the active DAW session selection with kind, ID, track, and time to mark timeline regions for transcript-driven edits.

Instructions

Highlight a DAW modifier: selection {kind, id?, track_id?, time?}; null or omit to clear.

Input Schema

NameRequiredDescriptionDefault
selectionNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • addedInput schema / properties / selection
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Selection"
+}
    • removedInput schema / properties / selection_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Selection Json"
-}
    • removedInput schema / required
      Removed value: -[
-  "project_path"
-]
  2. First observedv0.1.0

TDQS

C2.6/5.0
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. It reveals that this is a highlight/selection mutation and that null/omit clears state, but says nothing about persistence, side effects on existing selections, or whether this affects playback or editing state.

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?

A single compact sentence, front-loaded with the verb and the payload shape. Nothing is padded, though the alternative-to-clear clause could be separated for readability.

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?

An output schema exists, so return values needn't be described. But for a state-mutating tool with zero annotation coverage, an undocumented project_path parameter, and no explanation of what 'kind' can be, the description leaves too much for the agent to infer.

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 0% and the selection object is opaque (additionalProperties: true), so the inline shape {kind, id?, track_id?, time?} genuinely adds meaning the schema lacks. However, the second parameter project_path is never mentioned, and no semantics for 'kind' values are given.

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 verb 'highlight' plus the resource 'selection' gives the general purpose, and the inline shape hints at DAW-oriented state. But 'DAW modifier' is jargon and the description never distinguishes this from nearby siblings like set_session_region_tool or set_session_mode_tool.

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?

It states that null or omission clears the selection, which is a useful invocation hint. There is no guidance on when to use this versus set_session_region_tool or other selection-related siblings, and no prerequisites given.

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