Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

seek_session_tool

Move the open DAW playhead to a specified time position in a podcast project, optionally highlighting a selection or modifier for transcript-driven editing.

Instructions

Seek the open DAW playhead (no OS audio). Optional selection highlights a modifier.

Input Schema

NameRequiredDescriptionDefault
selectionNo
playhead_secYes
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"
-}
    • changedInput schema / required
      Previous value: -[
-  "project_path",
-  "playhead_sec"
-]New value: +[
+  "playhead_sec"
+]
  2. First observedv0.1.0

TDQS

C2.9/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 discloses one useful trait (no OS audio output), but says nothing about prerequisites (must a session be open?), whether the seek is synchronous, or how it interacts with concurrent playback.

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?

Two short, front-loaded sentences with no filler. The second sentence is terse to the point of ambiguity rather than wasteful.

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 need not be described, but with no annotations and 0% schema description coverage, the definition leaves the agent without prerequisites, parameter meaning, or failure behavior for a mutation-style session tool.

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% across three parameters, so the description must compensate. It hints at playhead_sec ('seek the playhead') and touches selection ('Optional selection highlights a modifier'), but never mentions project_path, and 'highlights a modifier' is too cryptic to define the selection object's shape or effect.

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?

States a specific verb and resource ('seek the open DAW playhead') and the parenthetical '(no OS audio)' separates it from playback siblings like play_audio_tool and set_session_playing_tool. It does not name a sibling explicitly, so it stops short of 5.

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?

'(no OS audio)' implies this is the playhead-move-without-playback option versus play_audio_tool, but no when-to-use/when-not rule or alternative is stated outright. Usage must be inferred from the parenthetical.

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