Skip to main content
Glama
pedraum

dropbox-transcripts-mcp

by pedraum

get_episode_tool

Retrieve the full transcript of a podcast episode by providing a guest name. Supports partial name matches, e.g., 'Fishman' returns 'Adam Fishman'.

Instructions

Get the full transcript for an episode by guest name. Supports partial matches: 'Fishman' will find 'Adam Fishman'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for get_episode_tool. Queries the database for an episode by name (with partial match fallback) and returns the full transcript.
    @mcp.tool()
    def get_episode_tool(name: str) -> str:
        """
        Get the full transcript for an episode by guest name.
        Supports partial matches: 'Fishman' will find 'Adam Fishman'.
        """
        conn = _get_conn()
        episode = get_episode(conn, name)
        if not episode:
            return f"No episode found for '{name}'. Use list_episodes to see all available names."
        return f"# {episode['name']}\n\n{episode['content']}"
  • The @mcp.tool() decorator registers get_episode_tool as an MCP tool on the FastMCP instance.
    @mcp.tool()
  • The database helper that get_episode_tool delegates to. First tries exact (case-insensitive) match, then falls back to partial LIKE match.
    def get_episode(conn: sqlite3.Connection, name: str) -> dict | None:
        # Exact match first
        row = conn.execute(
            "SELECT name, content, synced_at FROM episodes WHERE name = ? COLLATE NOCASE",
            (name,),
        ).fetchone()
        if row:
            return dict(row)
        # Partial match fallback
        row = conn.execute(
            "SELECT name, content, synced_at FROM episodes WHERE name LIKE ? COLLATE NOCASE ORDER BY name LIMIT 1",
            (f"%{name}%",),
        ).fetchone()
        return dict(row) if row else None
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses partial match behavior but lacks details on auth, rate limits, or side effects. Adequate but not comprehensive.

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?

Two sentences, no filler. Purpose and key behavior stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple (1 param, output schema exists). Description covers how to use and partial match behavior; output schema handles return format details.

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

Parameters5/5

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

Schema has 0% description coverage; description compensates by specifying 'guest name' and giving a concrete example of partial matching, adding essential meaning.

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?

Clear verb ('Get'), resource ('full transcript'), and method ('by guest name'). Distinguishes from siblings like list_episodes_tool, search_transcripts_tool, sync_tool.

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?

Implicitly states when to use: when you have a guest name and need a transcript. Lacks explicit exclusions or alternatives, but context from sibling names makes it clear.

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