Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_post_transcript

Extracts a public Facebook reel or video's own captions as text and timed segments from a URL, so you can read or process video transcripts without paid transcription.

Instructions

facebook: Transcript. GET /v1/facebook/post/transcript. Get a public Facebook reel or video's own captions as text and timed segments. No paid transcription. No captions costs 0 credits. 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": "facebook_post_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFacebook reel or video URL
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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose an unusually detailed cost model: 1 credit on success, 0 for empty/error/blocked/timeout/invalid/cache, plus the cache_max_age cost interaction. It still omits auth requirements, rate limits, or limits on video length/privacy, so it is strong but not complete.

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 and endpoint are correctly front-loaded, but the pricing block is repetitive ("No captions costs 0 credits" and "Costs 0 credits when transcript is empty" restate the same rule) and the closing sentence about not-found/empty charging is vague and partly contradicts the earlier zero-cost statement.

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?

For a two-parameter read tool with no output schema, the description covers the target resource, the return shape (text plus timed segments), and the complete cost profile, which is what an agent needs to decide and act. It lacks only ancillary operational details such as auth or failure-mode guidance beyond credits.

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%, so both 'url' and 'cache_max_age' are already documented in the schema; the description adds only the notion that the target must be a public reel or video. That is a marginal semantic addition over the structured fields, matching the baseline 3.

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 a public Facebook reel or video's own captions as text and timed segments" is a specific verb plus resource with the output shape stated, and it explicitly excludes paid transcription. It doesn't name a sibling (e.g. youtube_video_transcript / tiktok_video_transcript) as the alternative, but the platform scoping is clear enough to distinguish it from those tools.

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 implied rather than stated: fetch captions for a public Facebook reel/video, and it makes clear you should not expect paid transcription. There is no explicit when-not guidance (e.g. what to do when no captions exist, or when to pick the platform-specific sibling) beyond the cost note that an empty transcript is free.

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