Skip to main content
Glama
Podcast MCP
by calebn

find_replace_transcript_tool

Replace a literal word or phrase across every transcript track and recording, with optional preview and single-match replacement to review changes before applying.

Instructions

Replace a literal word or phrase everywhere in the transcript (Studio Find and replace).

Matches whole words across every track and recording; punctuation around a word is kept. dry_run returns the preview (matches, count, skipped_words) and changes nothing. Otherwise every previewed match is replaced through ReplaceTranscriptMatches in one undo step, and replaced gives the count. only is the 0-based position in the preview's matches of the one match to replace (the Find bar's Replace); it cannot be combined with dry_run. For one word use correct_transcript_tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "<search>",
      "replacement": "<replacement>"
    },
    "name": "find_replace_transcript_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNo
searchYes
dry_runNo
match_caseNo
replacementYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / only
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Only"
      +}
  2. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does it well: it discloses whole-word matching, punctuation preservation, preview payload fields (matches, count, skipped_words), that replacement goes through ReplaceTranscriptMatches in a single undo step, and the replaced count. It stops short of stating permission requirements or what happens with no matches, which keeps it from a 5.

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 purpose is front-loaded in the first clause, and each following sentence adds a distinct operational fact (scope, preview, undo behavior, single-match mode, alternative tool). No filler or restatement of the name.

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 need not be described, yet the description helpfully names the key fields. For a destructive mutation with no annotations, the main gaps are the unmentioned `match_case` and `project_path` parameters and no note on prerequisites or behavior when zero matches are found.

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 `search`, `replacement`, `dry_run`, and `only` (including 0-based indexing into the preview's matches), but says nothing about `match_case` or `project_path`, leaving two of six parameters undefined anywhere.

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 states a specific verb and resource ('Replace a literal word or phrase everywhere in the transcript') and ties it to the Studio Find and replace feature. It also explicitly distinguishes itself from correct_transcript_tool, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

It gives explicit modes of use: dry_run previews and changes nothing, default replaces all previewed matches, and `only` targets a single match from the preview. It also names the alternative tool and the condition that selects it ('For one word use correct_transcript_tool'), plus the exclusion that `only` cannot combine with `dry_run`.

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