Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook profile posts

facebook_profile_posts_list
Idempotent

Fetch posts from a public Facebook profile or Page, paginate with a cursor, and optionally host media to get delivery URLs.

Instructions

List posts from a Facebook profile or Page. Optional inputs: url, pageId, cursor and hostMedia. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_profile_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFull public Facebook profile or page URL.
cursorNoOpaque pagination cursor from a previous response.
pageIdNoFacebook page or profile id when you have it instead of a full URL.
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 post'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.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety is partly covered. The description adds genuinely non-structured context: a credit cost model (1 base, +2 per hosted asset, caps of 24/49) and the rule that failed assets are not surcharged, which also implicitly explains why readOnlyHint=false despite a list operation.

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 tight sentences, front-loaded with purpose then inputs then cost. Nothing is redundant, though the credits sentence is compressed enough that the cap notation ('up to 24 / 49 max') requires a second read.

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 paginated list tool with no output schema and full schema coverage, the definition covers what it does, how the target is identified, and the cost of optional media hosting. It omits what post fields are returned and any rate-limit or auth expectations, which are the only meaningful gaps.

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 parameter meaning is largely already supplied. The description mostly restates parameter names, with the one real addition being the surcharge implications of hostMedia, which goes beyond the schema's 90-day hosting note.

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 and resource: 'List posts from a Facebook profile or Page', which is immediately distinguishable from siblings like facebook_group_posts_list or facebook_profile_photos_list by the profile/Page scope. It does not explicitly name a sibling to route against, so it falls short of 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. facebook_group_posts_list or facebook_profile_get). The phrase 'Optional inputs: url, pageId, cursor and hostMedia' hints at call shape but not at the conditions that select this tool over its siblings.

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