Skip to main content
Glama
Podcast MCP
by calebn

list_session_suggestions_tool

Lists podcast session suggestions staged for an insert or replace target, filtered by pending, skipped, or accepted status, so you can review recordings before accepting them onto the timeline.

Instructions

List record sessions staged for an insert or replace target.

status: pending, skipped or accepted; empty lists all. A staged session has its recordings registered as sources but nothing on the timeline until accept_session_suggestion_tool places it.

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": "list_session_suggestions_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful domain state: a staged session has recordings registered as sources but nothing on the timeline until accepted. That is exactly the contextual insight an agent needs, though it never states the read-only nature explicitly (only implied by "List") and says nothing about ordering or result size.

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 scope sentence is front-loaded and the domain note is short and purposeful; every sentence adds information. The mid-sentence status fragment is slightly telegraphic but not wasteful.

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?

For a read-only list tool with an output schema (so return shape needn't be explained), the definition covers purpose, filter values, and staging semantics. The only real omissions are the project_path parameter and pagination/ordering behavior.

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 neither parameter is described in the schema, yet the description fully documents status with its accepted values (pending, skipped, accepted) and the empty/default behavior. The second parameter, project_path, gets no mention anywhere, so the compensation is only partial.

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 ("List record sessions staged for an insert or replace target") plus the scope of the query. It names the downstream sibling accept_session_suggestion_tool that consumes these sessions, which helps separate it from mutation siblings, though it doesn't address related suggestion tools like hear_session_suggestion_tool or skip_session_suggestion_tool.

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 rather than stated: it's a listing tool for staged sessions and accept_session_suggestion_tool is the action that commits one. There's no explicit when-to-use/when-not guidance or a note on which sibling to pick when you want a suggestion surfaced or rejected.

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