Skip to main content
Glama

Facebook: Post

facebook_post
Read-only

Facebook posts, videos and comments: post details, attachments, comments and replies.

Actions:

  • action=details: Get a Facebook post's text, author, timestamp, media, and reaction, comment and share counts. Start here for any post. If you need view counts, video download URLs or audio metadata (common for reels and videos), use action=details_extended instead. Pricing: 1 credit per call. Inputs: link (required).

  • action=details_extended: Get everything action=details returns plus view counts, HD/SD video URLs, music/audio metadata and author verification status. Use it for reels and video posts, or when the standard details lack view_count, video_hd_src or attached_track. Pricing: 1 credit per call. Inputs: link (required).

  • action=id: Extract the numeric post ID from a Facebook post URL. Use it to get the post_id that action=attachments needs. Pricing: 1 credit per call. Inputs: link (required).

  • action=attachments: List every media attachment (images and videos, with URLs and dimensions) on a Facebook post, including all items in multi-photo posts. Needs the numeric post_id from action=id. For the post's text and engagement, use action=details. Pricing: 5 credits per call (deeper scrape than standard post details). Inputs: post_id (required).

  • action=video: Get a Facebook video post's metadata: title, message text and hashtags, owner, reactions and view count. Needs the numeric video_id (the number in a facebook.com/.../videos/ URL, or from facebook_page (action=videos)). Pricing: 1 credit per call. Inputs: video_id (required).

  • action=comments: List top-level comments on a Facebook post or reel, with author, text, timestamp and reaction count. Returns up to 30 per call plus an end_cursor for the next page. Set include_reply_info=true to get the comment_feedback_id and expansion_token that action=comment_replies needs. Pricing: 1 credit per call. Inputs: link (required), limit (optional), end_cursor (optional), include_reply_info (optional).

  • action=comment_replies: List replies to one Facebook comment. Needs comment_feedback_id and expansion_token, which action=comments returns when called with include_reply_info=true. Pricing: 1 credit per call. Inputs: comment_feedback_id (required), expansion_token (required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoFacebook post or reel URL (regular posts, video posts and reels). Required for: details, details_extended, id, comments.
limitNoMaximum number of comments to return. Default: 10. Maximum: 30. Optional for: comments.
actionYesWhich operation to run. See the tool description for what each action returns and which parameters it needs.
post_idNoNumeric Facebook post ID, from action=id. Required for: attachments.
video_idNoNumeric Facebook video ID, e.g. the number in a facebook.com/.../videos/<id> URL. Required for: video.
end_cursorNoPagination cursor for next page of comments. Optional for: comments.
expansion_tokenNoExpansion token from the comments endpoint with include_reply_info=true. Required for: comment_replies.
include_reply_infoNoWhen "true", includes comment_feedback_id and expansion_token for fetching replies. Optional for: comments.
comment_feedback_idNoFeedback ID from the comments endpoint with include_reply_info=true. Required for: comment_replies.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesJSON response from the SocialAPIs REST endpoint, unchanged. Object or array depending on the endpoint; most include a `meta` block (statusCode, duration, creditsCharged, creditsRemaining).
creditsChargedNoCredits charged for this call, or null if the endpoint did not report it.
creditsRemainingNoCredits left on the API key after this call, or null if not reported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / comment_feedback_id / description
      Previous value: -"comment_replies (required): Feedback ID from the comments endpoint with include_reply_info=true."New value: +"Feedback ID from the comments endpoint with include_reply_info=true.\nRequired for: comment_replies."
    • changedInput schema / properties / end_cursor / description
      Previous value: -"comments (optional): Pagination cursor for next page of comments."New value: +"Pagination cursor for next page of comments.\nOptional for: comments."
    • changedInput schema / properties / expansion_token / description
      Previous value: -"comment_replies (required): Expansion token from the comments endpoint with include_reply_info=true."New value: +"Expansion token from the comments endpoint with include_reply_info=true.\nRequired for: comment_replies."
    • changedInput schema / properties / include_reply_info / description
      Previous value: -"comments (optional): When \"true\", includes comment_feedback_id and expansion_token for fetching replies."New value: +"When \"true\", includes comment_feedback_id and expansion_token for fetching replies.\nOptional for: comments."
    • changedInput schema / properties / limit / description
      Previous value: -"comments (optional): Maximum number of comments to return. Default: 10. Maximum: 30."New value: +"Maximum number of comments to return. Default: 10. Maximum: 30.\nOptional for: comments."
    • changedInput schema / properties / link / description
      Previous value: -"details, id (required): Facebook post URL. details_extended (required): Facebook post URL (works for reels, video posts, and regular posts). comments (required): Facebook post or reel URL."New value: +"Facebook post or reel URL (regular posts, video posts and reels).\nRequired for: details, details_extended, id, comments."
    • changedInput schema / properties / post_id / description
      Previous value: -"attachments (required): Numeric Facebook post ID, from action=id."New value: +"Numeric Facebook post ID, from action=id.\nRequired for: attachments."
    • changedInput schema / properties / video_id / description
      Previous value: -"video (required): Numeric Facebook video ID, e.g. the number in a facebook.com/.../videos/<id> URL."New value: +"Numeric Facebook video ID, e.g. the number in a facebook.com/.../videos/<id> URL.\nRequired for: video."
  2. Changed8 schema fields changed
    • changedInput schema / properties / comment_feedback_id / description
      Previous value: -"For comment_replies: Feedback ID from the comments endpoint with include_reply_info=true."New value: +"comment_replies (required): Feedback ID from the comments endpoint with include_reply_info=true."
    • changedInput schema / properties / end_cursor / description
      Previous value: -"For comments: Pagination cursor for next page of comments."New value: +"comments (optional): Pagination cursor for next page of comments."
    • changedInput schema / properties / expansion_token / description
      Previous value: -"For comment_replies: Expansion token from the comments endpoint with include_reply_info=true."New value: +"comment_replies (required): Expansion token from the comments endpoint with include_reply_info=true."
    • changedInput schema / properties / include_reply_info / description
      Previous value: -"For comments: When \"true\", includes comment_feedback_id and expansion_token for fetching replies."New value: +"comments (optional): When \"true\", includes comment_feedback_id and expansion_token for fetching replies."
    • changedInput schema / properties / limit / description
      Previous value: -"For comments: Maximum number of comments to return. Default: 10. Maximum: 30."New value: +"comments (optional): Maximum number of comments to return. Default: 10. Maximum: 30."
    • changedInput schema / properties / link / description
      Previous value: -"For details, id: Facebook post URL. For details_extended: Facebook post URL (works for reels, video posts, and regular posts). For comments: Facebook post or reel URL."New value: +"details, id (required): Facebook post URL. details_extended (required): Facebook post URL (works for reels, video posts, and regular posts). comments (required): Facebook post or reel URL."
    • changedInput schema / properties / post_id / description
      Previous value: -"For attachments: Numeric Facebook post ID, from action=id."New value: +"attachments (required): Numeric Facebook post ID, from action=id."
    • changedInput schema / properties / video_id / description
      Previous value: -"For video: Numeric Facebook video ID, e.g. the number in a facebook.com/.../videos/<id> URL."New value: +"video (required): Numeric Facebook video ID, e.g. the number in a facebook.com/.../videos/<id> URL."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare read-only, open-world, non-destructive behavior, and the description adds substantial context beyond them: per-action credit costs, comment pagination (up to 30 plus end_cursor), token prerequisites, and extra fields returned by details_extended. Nothing contradicts the annotations.

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 front-loaded with a summary and organized as a scannable action list, which suits a seven-action tool. It is somewhat verbose because 'Pricing: 1 credit per call' and 'Inputs:' are repeated for each action.

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?

Given the multi-action complexity, nine-parameter schema, and presence of an output schema, the description covers all operations, required inputs, pagination, prerequisites, and pricing. An agent has enough information to invoke each action correctly without return-value details.

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 schema already documents all nine parameters and their action-specific requirements. The description reinforces the action-to-parameter mapping and workflow dependencies (e.g. action=id produces post_id for attachments; include_reply_info produces tokens for comment_replies), adding useful consolidation beyond 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 opening sentence and action breakdown state a specific resource (Facebook posts, videos, comments) and the operations available, so the tool's general purpose is clear. It differentiates its internal actions but does not explicitly distinguish this tool from sibling tools such as facebook_page or facebook_media_download.

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

Usage Guidelines5/5

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

Each action has explicit when-to-use guidance: 'Start here for any post' for details, 'Use it for reels and video posts' for details_extended, and clear prerequisites for attachments and comment_replies. It also names alternatives within the action set, e.g. details_extended when view_count or video_hd_src is missing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.