Skip to main content
Glama
Sign In
facebook-mcp

facebook-mcp

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update Post

facebook_update_post
DestructiveIdempotent

Edit, publish, or reschedule a Facebook Page post your app created; dry-run previews and overwrite warnings prevent accidental changes.

Instructions

Edit a Page post the app itself created, or move it through the scheduled-post lifecycle. action:"edit" changes message/is_hidden/is_pinned; "publish_now" publishes a draft or scheduled post immediately; "reschedule" moves the publish time; "cancel_schedule" is not a Graph transition and is answered with the delete path to use instead. Dry run by default; an edit OVERWRITES the previous text, which Graph does not keep. Pinning is undocumented Graph behaviour and replaces the currently pinned post; the dry run names that post.

Input Schema

NameRequiredDescriptionDefault
applyNoSet true to actually perform the write. Omitted or false ⇒ the server decides from its configured write mode: usually a dry run that returns a plan preview and changes nothing, but a server (or package) configured apply-first performs the write. To be certain nothing happens, read the result: a dry run always reports the plan and says the write was NOT performed.
actionYesedit ⇒ change content (needs at least one of message, is_hidden, is_pinned). publish_now ⇒ publish a draft/scheduled post immediately, no other fields. reschedule ⇒ move the publish time, needs scheduled_publish_time and no content fields. cancel_schedule ⇒ NOT supported by Graph; the call explains that removing a scheduled post means deleting it with facebook_delete_post.
messageNoReplacement post text (action:"edit" only). This REPLACES the old text; the previous version is not recoverable through the API.
plan_idNoThe `planId` returned by a preceding dry-run preview of this same tool. Required for irreversible and spend-tier writes; plans expire a few minutes after they are created.
post_idYesThe post ID, normally "{page-id}_{post-id}". Only posts this same app created can be edited or deleted — a post made in the Facebook UI or by another app is not addressable here.
profileNoPage profile key (e.g. "brand-a") or a raw Page ID. Omitted ⇒ the default Page (FB_PAGE_ID).
is_hiddenNoaction:"edit" only. true ⇒ hide the post from the Page timeline without deleting it.
is_pinnedNoaction:"edit" only. true ⇒ pin the post to the top of the Page.
page_timezoneNoIANA timezone name of the Page (e.g. "Europe/Sofia"), used only to echo a scheduled instant in Page-local time next to UTC. Omitted ⇒ the server reads the Page's own timezone; if that read fails the echo is UTC-only.
scheduled_publish_timeNoaction:"reschedule" only. ISO-8601 WITH an explicit offset. Must be at least 10 minutes and at most 75 days ahead, and at most 29 days after the post was originally created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • addedInput schema / properties / post_id / pattern
      Added value: +"^(?=.*\\w)[\\w.-]+$"
    • changedInput schema / properties / scheduled_publish_time / description
      Previous value: -"action:\"reschedule\" only. ISO-8601 WITH an explicit offset. Must be more than 10 minutes and at most 75 days ahead, and at most 29 days after the post was originally created."New value: +"action:\"reschedule\" only. ISO-8601 WITH an explicit offset. Must be at least 10 minutes and at most 75 days ahead, and at most 29 days after the post was originally created."
  2. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, yet the description adds real context beyond them: edits OVERWRITE previous text that Graph does not retain, pinning replaces the currently pinned post (undocumented Graph behaviour), and the dry run names the affected post. The one gap is that it doesn't state the success/error shape for publish_now or reschedule, but the irreversibility and side effects are clearly disclosed.

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?

Front-loads what the tool does and the action lifecycle, then adds the risk notes (overwrite, pinning) at the end where they belong. It is dense but nearly every clause carries information; minor redundancy comes from re-listing which fields 'edit' changes when the schema already defines them.

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 10-parameter destructive mutation with no output schema, the description covers the critical unknowns: dry-run default, irreversibility of message edits, app-created-only addressability, and the pinning side effect. It stops short of describing what publish_now/reschedule return or what a dry-run plan contains, though plan_id's schema entry covers the plan flow.

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 100%, so every one of the 10 parameters is already documented, including the action enum, plan_id lifecycle, and the scheduled_publish_time constraints. The description restates the action semantics and the overwrite behaviour of message that the schema already carries, adding only the pinning side effect — so baseline 3 is appropriate.

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 ('Edit a Page post') plus a second capability set ('move it through the scheduled-post lifecycle'), then enumerates the four actions that scope the tool. It also carves out the boundary with facebook_delete_post by naming where cancel_schedule actually routes, so an agent can separate it from siblings without opening schemas.

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?

Explicitly maps each action to its condition of use ('publish_now' publishes a draft or scheduled post immediately; 'reschedule' moves the publish time; 'cancel_schedule' is not a Graph transition) and names the alternative tool to use instead. It also states the default execution mode (dry run by default), which is the key precondition for calling it.

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