facebook-mcp

Overview Schema Source Related Servers Discussions Admin

get_user_recent_posts

Retrieve a Facebook user's recent posts with text, UTC publish time, and permalink to review activity or gather content, ordered by publish time descending.

Instructions

List a user's recent posts (newest first), including text, UTC publish time and permalink. Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

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": {
      "username": "<username>"
    },
    "name": "get_user_recent_posts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`account`	No
`username`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses ordering (newest first) and the credential-set semantics of the account path plus its default, but says nothing about auth requirements, rate limits, or failure behavior when an account is absent.

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 sentences, front-loaded with the primary action and return contents. The second sentence is long but each clause carries real information about account resolution.

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 need not be restated, and the description does cover ordering and account resolution. However, with no annotations and 0% schema coverage it leaves the limit parameter and any failure/edge behavior undocumented.

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 0%, so the description must compensate. It does explain the account parameter well (credential set under ~/.facebook-mcp/accounts/<account>/, default configured account), but limit and its default of 10 go entirely unexplained in both schema and description.

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 (List) and resource (a user's recent posts) plus ordering and the fields returned, which implicitly separates it from get_user_latest_post_time. It never names that sibling explicitly, so the differentiation is left for the agent to infer.

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 guidance, no conditions, and no mention of the obvious alternative get_user_latest_post_time. The only contextual remark is about the account default, which is parameter behavior rather than usage routing.

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

Deploy Server