Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

post_get

Read-onlyIdempotent

Retrieve a single Facebook Page post by its ID to read its message, timestamps, link, picture, and share and reaction summaries.

Instructions

Read one post Read a single post by id (PageID_RecipientID). Returns the message, timestamps, link, picture, share and reaction summaries. Graph API: GET {post_id}.

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": {
      "post_id": "<post_id>"
    },
    "name": "post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
post_idYes
access_tokenNoOptional Facebook Page access token for this call only. Use it when the token you hold is not the one this server was configured with, or when the configured token has expired. Takes effect for this call and nothing else. Also accepted as token or page_token.
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the composite id format and the underlying Graph API call (GET {post_id}), but says nothing about permissions, paging, or error behavior for a missing/inaccessible post.

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?

The opening duplicates itself ("Read one post Read a single post by id"), wasting the front-loaded position on a restatement. The remainder is tight and the Graph API endpoint line is a useful anchor, but the redundant lead-in is avoidable.

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 enumerating returned fields is largely redundant, and the description is otherwise adequate for a simple single-object read. With two of four parameters undocumented in the schema and unaddressed in the description, it falls short of fully complete.

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 only 25% — only access_token is documented in the schema, while post_id, fields, and extra_fields are bare. The description partially compensates by explaining the post_id composite format, but leaves fields and extra_fields entirely unexplained.

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 states a specific verb and resource ("Read a single post by id") and even names the required id shape (PageID_RecipientID), so an agent can tell this is a single-object fetch rather than a list. It does not explicitly contrast itself with siblings such as page_posts_list or post_comments_list, so sibling differentiation is only implied.

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

Usage Guidelines3/5

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

Usage is implied by "Read a single post by id" — fetch one post when you already have its id. There is no explicit guidance on when to prefer this over page_posts_list, post_comments_list, or post_insights, and no stated prerequisites.

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