was-fb-mcp

fb_get_page_feed

Fetch recent posts published on a Facebook Page by providing the Page ID. Optionally set a limit (1-100) for number of posts.

Instructions

Fetch recent posts published on a Facebook Page.

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": {
      "pageId": "<pageId>"
    },
    "name": "fb_get_page_feed"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of posts to fetch (1-100)
`pageId`	Yes	Facebook Page ID
`pageToken`	No	Optional Page Access Token

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.5Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only says 'Fetch', implying read-only, but doesn't state pagination behavior, rate limits, authentication requirements (pageToken is optional per schema but not explained), or whether posts are ordered by time. The lack of detail leaves ambiguity.

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 with no extraneous words. It is appropriately concise but could benefit from a note on typical usage or return format without becoming verbose.

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?

No output schema is provided, and the description does not hint at what the response contains (e.g., an array of post objects with fields like message, created_time). Given the tool's complexity (3 parameters, 10 siblings), more context is needed to make it fully usable.

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 coverage is 100%, so the description does not need to explain parameters. However, it adds no extra meaning beyond the schema (e.g., that pageId is a numeric string). The description is too brief to complement the schema.

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 clearly states the tool fetches recent posts from a Facebook Page. It uses a specific verb ('Fetch') and identifies the resource ('recent posts published on a Facebook Page'). While it distinguishes from siblings like fb_create_post (create vs fetch), it could be more precise about the scope (only posts, not other feed items).

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?

No guidance on when to use this tool versus alternatives. Sibling tools like fb_get_post_comments or fb_get_insights exist but are not mentioned. There is no indication of prerequisites, excluded scenarios, or typical use cases.

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

Deploy Server