Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_get_recent_posts

Read-only

Fetch published Facebook Page posts along with their reactions, comments, and shares to review engagement and monitor content performance.

Instructions

List the Page's latest published posts with reactions, comments and shares.

:param limit: Number of posts (1-100, default 10). :param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fb_get_recent_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
page_idNo
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by naming the engagement metrics returned and by revealing the FB_PAGE_ID environment-variable fallback, but says nothing about token requirements, pagination, or rate limits.

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?

One summary sentence followed by three compact parameter lines; the core purpose is front-loaded and nothing is padded. The ':param' docstring residue is slightly mechanical but does not harm readability.

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

Completeness5/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 no explanation, and all three parameters are documented with defaults and constraints. For a simple read-only listing tool, an agent has everything needed to invoke it correctly.

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

Parameters4/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 carry the load, and it does: it gives the limit range (1-100) and default (10), marks page_id as optional with an environment-variable fallback, and marks the token as optional. It does not explain token acquisition or scopes, which keeps it from a 5.

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 and resource ('List the Page's latest published posts') and scopes the payload ('with reactions, comments and shares'). The word 'published' implicitly separates it from fb_get_scheduled_posts, but no sibling is named explicitly, so it falls just short of full differentiation.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as fb_get_scheduled_posts or fb_get_post_insights. Usage is only inferable from the word 'published' and the default-page-id note.

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