Skip to main content
Glama

savedthat

by app.savedthat
OverviewDiscussionsAdmin

Get a public transcript excerpt

get_public_transcript
Read-onlyIdempotent

Look up one video URL (YouTube, YouTube Shorts, Instagram Reels or TikTok) in SavedThat's public transcript index and return the opening excerpt of that transcript plus the link to its public page. Returns found=false when SavedThat has not processed the video. Only an excerpt is public; the full transcript is available to signed-in users in the app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesVideo URL on YouTube, Instagram Reels or TikTok.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
foundYes
titleNo
channelNo
excerptNo
platformNo
truncatedNo
transcript_page_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"The video URL."New value: +"Video URL on YouTube, Instagram Reels or TikTok."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "channel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "excerpt": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "platform": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "transcript_page_url": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "found"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: only an excerpt is public, the full transcript is gated behind sign-in, and a not-found result is expressed as found=false rather than an error.

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 tightly written sentences with the primary operation front-loaded, followed by the failure case and the public/excerpt limitation. No filler and nothing repeated from the schema or annotations.

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?

For a one-parameter lookup with a rich annotation set and an output schema, the description is complete: it covers what is fetched, what is returned, what the not-found sentinel is, and why only an excerpt is available. An agent can call this correctly without further information.

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?

There is a single required parameter at 100% schema description coverage, so the baseline is 3. The description does add platform scope (mentioning YouTube Shorts, which the schema's url description omits), but adds no format or normalization guidance for the URL.

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 (look up) and resource (one video URL in SavedThat's public transcript index) and names the exact return (opening excerpt plus public page link). It also enumerates the supported platforms, so the agent knows the scope of inputs immediately.

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?

The description clarifies the intended use case (single-URL lookup against the public index) and signals the failure mode (found=false when the video has not been processed), plus the scope boundary that full transcripts require sign-in. It does not explicitly contrast with the only sibling, get_product_info, but that tool is unrelated enough that no routing ambiguity exists.

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