Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_post

Fetches public Facebook reels or videos by URL and returns engagement counts, description, creation time, SD/HD video URLs, author, sound, and optional captions.

Instructions

facebook: Post. GET /v1/facebook/post. Get a public Facebook reel or video by URL (/reel/, /watch?v=, //videos/ and share links). Returns post_id, like_count (all reactions), comment_count, share_count, description, creation_time, the video's SD and HD URLs, author and sound. view_count is included only when the public page shows it; logged-out reel pages usually do not. shared_post_id and shared_post_url are null. Posts that Facebook only shows to Costs 1 credit when it succeeds. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the reel or video
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.
get_transcriptNoSet get_transcript=true for the reel's own captions (SRT) at no extra cost. Missing captions return transcript: null.
allow_long_transcriptionNoAccepted for compatibility and ignored. Transcripts are Facebook's own captions, never AI, at no extra cost.

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 behavioral burden and does substantial work: it discloses the per-call credit cost on success, that errors/blocked/timeout/invalid requests and cache hits are free, that view_count is only sometimes present, and that shared_post_id/shared_post_url are always null. The sentence beginning "Posts that Facebook only shows to" is truncated and leaves a caveat incomplete, which prevents 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.

Conciseness3/5

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

Purpose and endpoint are front-loaded, which is good, but the body is a single dense run-on that mixes return fields, null-value caveats, and pricing. One clause is cut off mid-sentence ("Posts that Facebook only shows to"), which is wasted or broken text rather than useful content.

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 4-parameter read tool with no output schema, the description enumerates the returned fields and their availability caveats plus the full cost model, which is close to what an agent needs. The truncated caveat about restricted posts is the main completeness gap.

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 100%, so the schema already explains url, cache_max_age, get_transcript, and allow_long_transcription, making 3 the baseline. The description reinforces the credit implications of caching and captions but adds no 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.

Purpose4/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 ("Get a public Facebook reel or video by URL") and enumerates the accepted URL shapes (/reel/, /watch?v=, /<page>/videos/, share links), so the agent knows exactly what content this retrieves. It does not name the sibling facebook_post_transcript or explain how it relates to it, which keeps it below a 5.

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 context is implied by the URL-pattern list and the 'public' qualifier, and the credit model tells the agent when a call is free. However, there is no explicit when-to-use vs. when-to-use-an-alternative guidance, and no statement of preconditions such as what happens with private or login-gated posts.

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