Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook profile reels

facebook_profile_reels_list
Idempotent

Lists Reels from a public Facebook profile or Page URL, supports cursor-based pagination, and can optionally host source media for delivery.

Instructions

List Reels from a Facebook profile or Page. Requires url. Credits: 1 base; hostMedia=true adds +2 per hosted asset (up to 24 / 49 max). Failed assets are not surcharged.

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_profile_reels_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Facebook profile or page URL whose reels should be listed.
cursorNoOpaque pagination cursor from a previous response.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
hostMediaNoWhen true, hosts source media for 90 days and returns delivery URLs in each reel's `hostedMedia`.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the credit cost model, the surcharge for hosted assets, the cap, and that failed assets are not billed — genuinely useful operational context an agent cannot get from structured fields. It does not explain why readOnlyHint is false (the media-hosting side effect) or describe pagination behavior, leaving some behavioral ground uncovered.

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?

Three short sentences with the core purpose front-loaded and cost details compressed into one line; nothing is padded. The parenthetical "(up to 24 / 49 max)" is slightly ambiguous about what the two numbers cap, which keeps it off a 5.

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?

With six parameters all documented at 100% coverage, annotations covering safety and openness, and no output schema, the description's main remaining duties are cost and input requirements, both of which it handles. It omits any hint of the response shape or pagination flow, which is a modest gap for a list tool.

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 documents url, cursor, hostMedia, context, llm_model, and conversation_id, establishing a baseline of 3. The credit sentence does add a cost tradeoff meaning to hostMedia beyond the schema's description of the 90-day hosting, but no other parameter gains meaning from the description.

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 opens with a specific verb+resource ("List Reels from a Facebook profile or Page") and states the required input, which cleanly separates it from siblings like facebook_profile_photos_list and facebook_profile_posts_list. It stops short of naming an alternative outright, so it is clear but not maximally differentiating.

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 by the resource scope (a public profile or Page URL), but there is no explicit when-to-use/when-not guidance and no comparison to the Instagram reels siblings or to facebook_profile_get. The agent must infer the selection conditions from the tool name and schema.

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