Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook post or reel

facebook_post_get
Read-onlyIdempotent

Fetch a public Facebook post or Reel by URL to retrieve its content, with optional top-level comments and video transcript.

Instructions

Get a Facebook post or Reel by URL. Requires url.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public permalink to the Facebook post or reel.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
includeCommentsNoWhen true, includes a sample of top-level comments when available.
includeTranscriptNoWhen true, includes a plain-text transcript when available for the video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered without the description. Beyond that, the description adds essentially nothing: it does not mention what is returned, that comments/transcript are opt-in via flags, or any rate-limit or auth expectations for public permalinks.

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

Conciseness4/5

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

Two short sentences with the resource and the required input front-loaded and no filler. It is efficiently written, though the brevity comes at the cost of the missing behavioral detail scored elsewhere.

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

Completeness2/5

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

For a fetch tool with six parameters, a conversation_id sequencing requirement, and no output schema, the description should say what comes back (post body, media, author) and what the includeComments/includeTranscript flags do. None of that is present, so an agent must reconstruct behavior entirely from the schema and annotations.

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 all six parameters (including context, llm_model, and the conversation_id workflow) are already documented in the schema. The description only restates the required `url` and adds no meaning beyond it, which is the baseline 3 case.

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 Facebook post or Reel by URL' — which tells an agent it retrieves post content itself rather than a transcript or comment thread. It stops short of naming the sibling tools (facebook_post_transcript_get, facebook_post_comments_list) that would disambiguate it explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives such as the transcript or comments tools even though those siblings exist. 'Requires `url`' is a precondition, not usage guidance.

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