Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_publish_post

Publish or schedule Facebook Page posts with text, links, or photos, including local or URL images and future timing. Confirm content and timing before posting publicly.

Instructions

Publish or schedule a Page post: text, text + link, or photo (local file or URL). This is public: confirm content and timing with the user first.

:param message: Post text / photo caption. :param link: Optional URL to attach (text posts only). :param photo_path: Optional local image path (jpg, png, gif, webp...). :param photo_url: Optional public image URL. Use photo_path or photo_url, not both. :param scheduled_publish_time: Optional UNIX seconds, at least 10 minutes ahead. :param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token.

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": {
      "message": "<message>"
    },
    "name": "fb_publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNo
messageYes
page_idNo
photo_urlNo
photo_pathNo
page_access_tokenNo
scheduled_publish_timeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, so the description's job is added context — and it delivers the key one: the action is publicly visible and needs user confirmation. It also adds a timing constraint (at least 10 minutes ahead) that annotations cannot express. It stops short of stating permission requirements for the token or what happens on duplicate publishes.

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?

Purpose and the public-visibility warning are front-loaded ahead of the parameter list, so the highest-risk information is read first. The docstring-style ':param' block is slightly verbose in format but each line adds a constraint rather than restating the field name.

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?

For a 7-parameter public mutation with an output schema (so return values need no explanation), the definition covers what to send, when to confirm, and the scheduling floor. Remaining gaps are secondary: required token scopes and the timezone/interpretation of scheduled_publish_time relative to the Page.

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

Parameters5/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 all seven parameters, and it does: message, link (flagged as text-posts-only), photo_path with accepted formats, photo_url with the either/or rule, scheduled_publish_time in UNIX seconds with a minimum lead time, page_id with its FB_PAGE_ID default, and the token. The added constraints (mutual exclusion, 10-minute floor, default fallback) are meaning the schema does not provide.

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 first sentence states a specific verb+resource pair (publish/schedule a Page post) and enumerates the supported content shapes: text, text + link, and photo via local file or URL. That is enough to separate it from video publishing, but no sibling is named, so an agent must infer the boundary with fb_publish_video or fb_publish_scheduled_now.

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?

"This is public: confirm content and timing with the user first" is a real precondition that changes agent behavior before calling, and "Use photo_path or photo_url, not both" resolves an obvious ambiguity. What's missing is routing guidance for the schedule-vs-publish-now case, where fb_publish_scheduled_now is the likely alternative.

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