Skip to main content
Glama
pedraum

dropbox-transcripts-mcp

by pedraum

list_episodes_tool

List all available podcast transcript episodes indexed from Dropbox, providing a complete overview to select specific episodes for search or review.

Instructions

List all available podcast transcript episodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'list_episodes_tool'. Decorated with @mcp.tool(), it retrieves all episodes from the database by calling list_episodes(conn), gets the last sync time via get_last_sync(conn), and returns a formatted string listing all episode names with a header showing count and sync status.
    @mcp.tool()
    def list_episodes_tool() -> str:
        """List all available podcast transcript episodes."""
        conn = _get_conn()
        episodes = list_episodes(conn)
        last_sync = get_last_sync(conn)
        header = f"{len(episodes)} episodes indexed (last synced: {last_sync or 'never'})\n\n"
        return header + "\n".join(e["name"] for e in episodes)
  • The tool is registered with FastMCP via the @mcp.tool() decorator on line 60, which makes it available as an MCP tool named 'list_episodes_tool'.
    @mcp.tool()
    def list_episodes_tool() -> str:
  • The list_episodes function queries the database for all episodes (name and synced_at), ordered by name, and returns them as a list of dicts. This is the data retrieval helper used by list_episodes_tool.
    def list_episodes(conn: sqlite3.Connection) -> list[dict]:
        rows = conn.execute("SELECT name, synced_at FROM episodes ORDER BY name").fetchall()
        return [dict(r) for r in rows]
  • The get_last_sync function retrieves the last sync timestamp from the sync_state table, used by list_episodes_tool to display when episodes were last synced.
    def get_last_sync(conn: sqlite3.Connection) -> str | None:
        row = conn.execute("SELECT value FROM sync_state WHERE key = 'last_sync'").fetchone()
        return row["value"] if row else None
  • The tool has no input parameters (empty signature) and returns a plain string. The docstring serves as the description for the MCP tool.
    def list_episodes_tool() -> str:
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 only states 'list all available' without disclosing behavioral traits (e.g., pagination, rate limits, whether it's a snapshot). Minimal transparency beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that is front-loaded with the essential purpose. Every word earns its place with no verbosity.

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?

Given the tool's simplicity (no parameters, output schema exists), the description is mostly adequate. It could hint at the return structure (list of episodes), but the output schema covers that. Missing details like order or limits are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is 100%. Baseline for zero parameters is 4. The description adds context about the resource type but does not need to elaborate further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List' and the resource 'all available podcast transcript episodes'. It distinguishes from siblings like get_episode_tool (single episode) and search_transcripts_tool (search).

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?

The description implies usage for retrieving all episodes but offers no explicit guidance on when to use this tool versus alternatives like get_episode_tool or search_transcripts_tool. No when-not or prerequisite information is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pedraum/dropbox-transcripts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server