Skip to main content
Glama
Sign In

SavedThat

by app.savedthat
OverviewDiscussionsAdmin

Get the full transcript of a saved video

get_my_transcript
Read-onlyIdempotent

Return the entire transcript of one video the user saved. get_moment is the better fit for a specific moment, since a full podcast transcript can run to tens of thousands of words. Use this when the user asks for the whole thing. When the video has no speech at all, source comes back visual and the text is the SavedThat indexer's own scene and on-screen-text pass, not the creator's words: describe it rather than quoting it.

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": {
      "url": "<url>"
    },
    "name": "get_my_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe saved video URL.

Output Schema

NameRequiredDescriptionDefault
fullNo
foundYes
sourceNo
transcriptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses output magnitude ('tens of thousands of words') and, importantly, the provenance semantics of the `source` field — `visual` means indexer-generated scene/on-screen-text text, not creator speech, and should be described rather than quoted. That is behavior-shaping context an agent could not infer from structured fields alone.

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?

Three sentences, front-loaded with the core action, then the alternative, then the caveat. No filler; the longer final sentence earns its length by covering a real edge case.

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?

An output schema exists so return values need no explanation, yet the description still clarifies the one semantically tricky field (`source`) and the size expectation. Nothing an agent needs to call this correctly or interpret the result is missing.

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 coverage is 100% with a single required `url` parameter already documented, so the schema carries the parameter burden. The description only implies that the URL must reference one of the user's saved videos, adding little syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Return the entire transcript of one video the user saved') and immediately contrasts scope with the sibling get_moment, which handles a specific moment. An agent can distinguish the two without consulting 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?

Gives an explicit selection rule ('Use this when the user asks for the whole thing') and names the alternative tool plus the condition that favors it. It also flags the edge case of videos with no speech, which changes how the result should be presented.

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

All SavedThat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources