Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_profile_posts

Retrieve a public Facebook page's timeline posts, three per page and newest first, including text, URLs, author, reaction/comment/share counts, publish time, and video URLs.

Instructions

facebook: Profile Posts. GET /v1/facebook/profile/posts. Get a public Facebook page's timeline posts, 3 per page, newest first, as a signed-out visitor sees them: id, text, url, author, reactionCount, commentCount, shareCount, publishTime, and SD/HD video URLs with a thumbnail for videos and reels. Provide url or pageId (the id from /v1/facebook/profile). topComments is always empty and videoViewCount is null: the signed-out feed does not carry them. Pass cursor from a res Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlNoThe URL of the public Facebook page
cursorNoThe cursor from the previous response, to get the next 3 posts
pageIdNoThe page's numeric id (id from /v1/facebook/profile). Saves reading the page first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the signed-out limitation (topComments always empty, videoViewCount null), page size and ordering, and a detailed cost model including which failures are free. It omits auth/rate-limit expectations beyond the 'signed-out visitor' framing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the operation name and endpoint, and most sentences carry useful facts. However, the sentence 'Pass cursor from a res' is truncated mid-word, and the 'facebook: Profile Posts. GET /v1/...' header partially duplicates the description text.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the returned fields (id, text, url, author, counts, publishTime, video URLs/thumbnail) and covering pagination and billing. The broken cursor sentence is the one gap an agent would notice when paginating.

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 coverage is 100%, so the baseline is 3; the description adds real value by clarifying that url or pageId must be supplied (important since the schema marks zero required parameters) and by defining cursor as the next-page token from the previous response.

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 ('Get a public Facebook page's timeline posts') and pins the scope tightly: 3 per page, newest first, signed-out visitor view. It also references the sibling endpoint /v1/facebook/profile for the pageId, so an agent can separate it from facebook_profile and facebook_post.

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?

Explains how to invoke it (provide url or pageId, with the note that pageId 'saves reading the page first') and what the data represents. It stops short of explicit when-not guidance or naming an alternative feed tool, so selection against siblings is only implied.

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

Deploy Server

Other Tools