Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook profile photos

facebook_profile_photos_list
Idempotent

Lists photos from a public Facebook profile or Page by URL, with optional pagination and 90-day media hosting for returned assets.

Instructions

List photos 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_photos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Facebook profile or page URL whose photos 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 photo'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.8/5.0
Behavior4/5

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

Annotations already declare openWorldHint, idempotent, non-destructive, and readOnlyHint=false, so the safety profile is largely covered. The description adds genuinely new behavioral information the annotations lack: the credit cost model (1 base, +2 per hosted asset, caps of 24/49) and the fact that failed assets are not surcharged. Minor tension in that a 'list' tool is marked readOnlyHint=false, but that is consistent with media hosting side effects rather than a description contradiction.

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, front-loaded with what the tool does, then the hard requirement, then the cost model. The 'Requires `url`' sentence largely duplicates the schema's required list, a small redundancy, but nothing is padded.

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?

Six parameters with full schema descriptions and no output schema; the schema covers cursor pagination, context, llm_model, and the 90-day hosting detail. The description supplies the missing cost dimension, so an agent has enough to call it correctly, though pagination behavior in the description is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds cost semantics for `hostMedia` (the +2 per hosted asset and cap) that the schema does not convey, which materially affects how an agent sets that flag. `url` being required is repeated from the schema but is harmless.

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?

States a specific verb and resource ('List photos from a Facebook profile or Page') with the scope of the target object. It is clearly distinguishable from sibling listing tools (posts, reels, events) by the resource name, though it never explicitly routes against them.

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 only implied: the caller should use it when they have a public Facebook profile/Page URL and want photos. There is no explicit when-not guidance, no mention of pagination workflows, and no steering to or away from the many sibling list tools.

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