Skip to main content
Glama
Podcast MCP
by calebn

list_edit_decisions_tool

List pending podcast edit decisions with Review fields and filter by project, applied status, reason prefix, or review requirement to identify edits awaiting approval.

Instructions

List pending decisions with Review fields; archived edits are in list_applied_edits_tool.

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_edit_decisions_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
appliedNo
project_pathNo
reason_prefixNo
review_requiredNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'List' implies a non-mutating read but that is never stated, and nothing covers ordering, pagination, volume, or access requirements. The output schema covers return shape, which lifts this above a pure gap, but mutation/safety semantics are left to inference.

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 compact sentence with the primary scope front-loaded and the alternative tool name attached after a semicolon. Nothing is padded, though the terseness trades away detail the agent actually needs.

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?

With an output schema present, return values need not be described, and the sibling pointer is helpful. However, a four-parameter filtering tool with zero schema coverage and an unexplained 'applied' filter that appears to contradict the pending-only description leaves meaningful gaps.

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 four parameters, so the description must compensate and largely does not: applied, project_path, reason_prefix, and review_required are never mentioned. 'With Review fields' is at best a faint nod to review_required, and the 'applied' filter actively conflicts with the stated pending-only scope.

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 pending decisions') plus a content hint ('with Review fields'), and explicitly separates itself from list_applied_edits_tool as the archive view. The only ambiguity is the vocabulary shift between 'decisions' and 'edits', which makes the object being listed slightly fuzzy.

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 names one alternative and the condition that selects it (archived edits go to list_applied_edits_tool), which is real routing guidance. But it never says when this tool is the right choice beyond 'pending', and the presence of an 'applied' boolean parameter directly muddies the pending-only framing without explanation.

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