Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_photos_list

Read-onlyIdempotent

List photos posted to a Facebook Page and retrieve image URLs, captions, and comment counts for page management and content review.

Instructions

List a Page's photos List photos posted to a Page, with image URLs, captions and comment counts. Graph API: GET {page_id}/photos.

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": {
      "page_id": "<page_id>"
    },
    "name": "page_photos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
sinceNo
untilNo
fieldsNo
page_idYes
access_tokenNoOptional Facebook Page access token for this call only. Use it when the token you hold is not the one this server was configured with, or when the configured token has expired. Takes effect for this call and nothing else. Also accepted as token or page_token.
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered and the description does not contradict it. What the description adds is limited to the shape of the returned items; it says nothing about pagination behavior despite having after/limit/since/until parameters, nor about how token scoping or permission failures surface.

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?

It is short and front-loaded, but the opening is mangled: "List a Page's photos List photos posted to a Page" duplicates the title fragment into the description, wasting the most salient position on redundancy. The endpoint reference at the end is compact and useful.

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?

An output schema exists, so return values need not be re-explained, but with 8 parameters and near-zero schema coverage the description leaves the pagination and field-selection surface completely opaque. For a list tool that an agent will almost always need to paginate, the absence of any guidance on the cursor and time-window parameters is a substantive completeness gap.

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

Parameters2/5

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

Schema description coverage is only 13% across 8 parameters; the sole documented parameter is access_token, and the description adds no meaning for limit, after, since, until, fields or extra_fields. It does not explain that since/until are likely Unix timestamps, what fields/extra_fields override, or that after is a cursor, so it fails to compensate for the schema gap.

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 ("List photos posted to a Page") plus the concrete payload ("image URLs, captions and comment counts") and the underlying Graph API path. It is unambiguous about what it does, but it never distinguishes itself from the near-identical siblings page_videos_list or page_albums_list, 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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as page_posts_list or post_get. The only contextual signal is the raw endpoint "GET {page_id}/photos", which assumes the agent already knows the Graph API rather than telling it when this tool is the right pick.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.