Skip to main content
Glama

Create Facebook Page Post

meta_create_post

Create a Facebook Page post with text, optional link, and scheduling. Supports instant publishing or saving as draft.

Instructions

Creates a new post on a Facebook Page.

Requires: meta_list_pages must be called first to load page tokens.

Args:

  • page_id (string): Facebook Page ID to post to

  • message (string): Text content of the post

  • link (string, optional): URL to attach to the post (creates a link preview)

  • published (boolean, optional): If false, saves as draft. Default true.

  • scheduled_publish_time (number, optional): Unix timestamp for scheduling (must be 10 min to 30 days in future; published must be false)

Returns: Post ID of the created post.

Notes:

  • Maximum post length: ~63,206 characters

  • Scheduling requires the page to have Page Publishing Authorization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesFacebook Page ID
messageYesPost text content
linkNoOptional URL to share
publishedNoPublish immediately (true) or save as draft (false)
scheduled_publish_timeNoUnix timestamp to schedule the post (requires published=false)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description accurately portrays a write operation with no destructive side effects. It adds details like maximum character count, scheduling requirements, and the need for Page Publishing Authorization, which go beyond annotations.

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

Conciseness5/5

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

The description is well-structured with a clear purpose, prerequisites, parameter list, return value, and notes. It is concise and front-loaded with essential info.

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?

For a post creation tool with no output schema, the description adequately covers return value (Post ID), parameters, constraints, and prerequisites. No gaps identified.

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 baseline is 3. The description adds significant value by explaining the prerequisites for page_id, the behavior of link (creates preview), the draft vs publish distinction for published, and the scheduling constraints for scheduled_publish_time. However, response_format is not elaborated in description.

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?

The description clearly states 'Creates a new post on a Facebook Page' and details the parameters and behavior. It distinguishes itself from sibling tools like meta_create_photo_post and meta_create_video_post by focusing on text/link posts.

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?

The description explicitly requires calling meta_list_pages first for tokens and notes scheduling constraints and authorization. It implies usage for text/link posts but does not explicitly exclude other scenarios or compare with similar siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server