Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_comments_tool

List timeline review comments sorted by start time to build agent work queues or find open action items. Filter resolved comments or show only incomplete actions, with IDs, authors, tracks, and status.

Instructions

List timeline review comments sorted by timeline_start.

Pass include_resolved=false for an agent work queue, or open_actions_only=true for incomplete action items. Each row includes id, body, author, track_ids, action_items, resolved_*.

Input Schema

NameRequiredDescriptionDefault
project_pathNo
include_resolvedNo
open_actions_onlyNo

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

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the sort order and lists the row fields returned, which is useful, but says nothing about permissions, result limits, or pagination behavior for what is evidently a read-only listing tool.

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?

Front-loads what the tool does, then usage, with no filler sentences. The 'Each row includes...' enumeration is slightly redundant given an output schema exists, but it is brief and harmless.

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, so return values needn't be re-explained. The description covers purpose, sort, and the two filter parameters' intent, making it nearly complete for a simple listing tool; the only real gap is the undocumented project_path parameter.

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 description coverage is 0%, so the description must compensate. It explains include_resolved (false → agent work queue) and open_actions_only (true → incomplete action items), covering two of three parameters, but leaves project_path entirely undefined. Partial compensation warrants a 3.

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 (List) and resource (timeline review comments) plus the sort order (timeline_start), so an agent immediately knows this is a read/enumeration tool. It does not name a sibling such as get_comment_tool to differentiate scope, but the list-vs-get distinction is inherent and the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit scenario-based guidance: 'Pass include_resolved=false for an agent work queue, or open_actions_only=true for incomplete action items.' This tells the agent which filter mode to pick for which intent. It stops short of naming when NOT to use the tool or pointing to an alternative sibling.

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