Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_post_transcript

Extracts the spoken-word transcript from a Reddit video post by URL, with optional language selection, so you can read or search video content without watching it.

Instructions

reddit: Post Transcript. GET /v1/reddit/post/transcript. Get the transcript from a Reddit video post Costs 1 credit when it succeeds. Costs 0 credits when transcript is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": "reddit_post_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesReddit post URL or direct v.redd.it video URL
languageNoTwo-letter language code. Defaults to en.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the billing model in unusual detail: 1 credit on success, 0 for empty transcripts, and 0 for errors, blocked, timed-out, invalid and cached requests. It says nothing about response shape (plain text vs. timed segments), auth requirements, or rate limits, which are the bigger behavioral unknowns for a transcript fetch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause and the route is given immediately, which is good. The remaining four billing sentences are verbose and partly redundant, and they slightly undercut each other (“Costs 0 credits when transcript is empty” versus “A not-found or empty result is charged only where that operation's published cost says so”), forcing the agent to reconcile them.

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

Completeness3/5

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

For a simple single-fetch tool this is close to adequate, but with no annotations and no output schema the description should say what a successful call returns (transcript text, language, timing) and whether a not-found video errors or returns empty. As written, the agent knows the price but not the payload.

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% and all three parameters (url, language, cache_max_age) are documented in the schema with an example URL, so the baseline of 3 applies. The description adds no parameter meaning beyond restating the credit consequence of cache_max_age.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get the transcript from a Reddit video post" gives a specific verb and resource, and the platform qualifier separates it from youtube_video_transcript, tiktok_video_transcript and facebook_post_transcript. It stops short of naming the sibling to use for non-transcript Reddit data (e.g. reddit_post), so the differentiator is implied by naming rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer the tool applies to Reddit video posts and direct v.redd.it URLs, and the credit rules tell it what a call will cost. There is no explicit when-to-use or when-not guidance, and no pointer to alternatives if the agent actually needs post text or comments.

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