meta-mcp

List posts on a Facebook Page

page_posts

Retrieve posts from a Facebook Page using edges like published_posts, posts, feed, or tagged. Filter by time, fields, and paginate results.

Instructions

Default edge is published_posts (Page-owned posts paged by created time). Other edges: posts (default Graph posts edge), feed (everything on the wall, including visitor posts), tagged (posts where the page is tagged).

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

Input Schema

Name	Required	Default
`page_id`	Yes
`edge`	No	published_posts
`fields`	No
`since`	No
`until`	No
`limit`	No
`auto_paginate`	No
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must disclose behaviors. It mentions 'paged by created time' for the default edge, but does not explain pagination behavior (auto_paginate, max_pages), authentication needs, rate limits, or response structure. The transparency is adequate but missing key details.

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?

The description is a single sentence plus a list of edge options. It is concise and front-loaded with the default edge. However, a bulleted list for edges would improve scannability. Overall, it earns its place without wasted words.

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?

Given the complexity (8 parameters, no output schema, no annotations), the description is incomplete. It does not cover return format, authorization, pagination behavior, or most parameters. The edge differentiation is useful, but the agent needs more context to use all parameters correctly.

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 coverage is 0%, so the description should explain all parameters. It only covers the 'edge' parameter with enum values. Parameters like page_id, fields, since, until, limit, auto_paginate, and max_pages are not described, leaving the agent to guess their purpose.

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?

The description clearly states the tool lists posts on a Facebook Page and distinguishes multiple edge types (published_posts, posts, feed, tagged), each with a brief explanation. This differentiates it from sibling tools like post_get and post_comments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description explains each edge option and what content it returns, guiding the agent on when to use which edge for different post types. It lacks explicit prerequisites or when-not-to-use guidance, but the edge descriptions are sufficient for most use cases.

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