Skip to main content
Glama
pedraum

dropbox-transcripts-mcp

by pedraum

search_transcripts_tool

Search all podcast transcripts for specific terms or phrases. Returns matching episodes with highlighted snippets. Supports quoted exact matches, AND/OR logic, and prefix wildcards like 'retain*'.

Instructions

Full-text search across all transcript content. Returns matching episodes with highlighted snippets. Supports quoted phrases, AND/OR operators, and prefix wildcards (e.g. 'retain*').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that performs full-text search across all transcript content using FTS5. It delegates to search_episodes() and formats results with highlighted snippets.
    @mcp.tool()
    def search_transcripts_tool(query: str, limit: int = 5) -> str:
        """
        Full-text search across all transcript content.
        Returns matching episodes with highlighted snippets.
        Supports quoted phrases, AND/OR operators, and prefix wildcards (e.g. 'retain*').
        """
        conn = _get_conn()
        results = search_episodes(conn, query, limit)
        if not results:
            return "No results found."
        parts = [f"## {r['name']}\n{r['snippet']}" for r in results]
        return f"Found {len(results)} result(s) for '{query}':\n\n" + "\n\n---\n\n".join(parts)
  • Registration via the @mcp.tool() decorator on a FastMCP instance, which registers the function as an MCP tool.
    @mcp.tool()
  • Helper function that executes the FTS5 search query on the episodes_fts virtual table, returning episode names and highlighted snippets.
    def search_episodes(conn: sqlite3.Connection, query: str, limit: int = 5) -> list[dict]:
        rows = conn.execute(
            """
            SELECT e.name,
                   snippet(episodes_fts, 1, '[', ']', '...', 40) AS snippet
            FROM episodes_fts
            JOIN episodes e ON e.id = episodes_fts.rowid
            WHERE episodes_fts MATCH ?
            ORDER BY rank
            LIMIT ?
            """,
            (query, limit),
        ).fetchall()
        return [dict(r) for r in rows]
Behavior3/5

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

With no annotations, the description discloses query syntax features (quoted phrases, operators, wildcards), which is helpful. However, it omits other behavioral aspects like whether it is read-only, pagination behavior, or performance implications.

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 three concise sentences: purpose, output, and supported features. No superfluous information, well-structured.

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 presence of an output schema (not shown) and simple parameters, the description covers purpose, output type, and query syntax. It lacks details on result ordering or pagination, but overall sufficient.

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?

The schema has 0% description coverage, so the description must compensate. It explains query capabilities but does not describe the limit parameter beyond its default. Partial compensation.

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 it performs full-text search across all transcript content and returns matching episodes with highlighted snippets. It distinguishes itself from sibling tools like get_episode, list_episodes, and sync by specifying search capabilities.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention when not to use it or refer to sibling tools for specific use cases.

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