Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_posts_list

Read-onlyIdempotent

List posts published by a Facebook Page, newest first, with messages, timestamps, engagement counts, and attachment metadata. Filter by date and paginate results with limit and after.

Instructions

List a Page's posts List posts published by a Page, newest first, with message, timestamp, engagement counts and attachment metadata. Filter by date with since/until (Unix timestamps), paginate with limit and after. Graph API: GET {page_id}/posts.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
sinceNo
untilNo
fieldsNo
page_idYes
include_ownNo
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is pre-covered. The description adds genuinely useful behavior: newest-first ordering, the payload contents (message, timestamp, engagement counts, attachment metadata), and the pagination model. It says nothing about permissions required beyond the token note, rate limits, or what happens with very large result sets.

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 dense sentences that front-load the resource and payload before moving to filtering and pagination; every clause carries information. The opening is slightly redundant ('List a Page's posts List posts published by a Page'), a duplicated fragment that could be trimmed.

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

Completeness3/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 needn't be explained, and the filtering/pagination story is adequate. But with 9 parameters and 3 of them (fields, extra_fields, include_own) undocumented anywhere, the definition leaves meaningful ambiguity for a tool whose main flexibility comes from those parameters.

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 only 11% (just access_token), so the description has to compensate. It does explain since/until as Unix timestamps and assigns roles to limit and after, but fields, extra_fields, and include_own are undocumented in both the schema and the description — an agent cannot know what these do or how they interact with the default returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a Page's posts'), adds ordering ('newest first'), names the returned fields, and cites the underlying endpoint 'GET {page_id}/posts'. An agent can tell this apart from post_get or post_comments_list without opening the schema.

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?

The description implies usage by explaining date filtering with since/until and pagination with limit/after, so the mechanics of a typical listing flow are covered. However, it never says when to choose this tool over post_get, page_insights, or pages_list, and gives no prerequisites beyond the endpoint string.

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