meta-mcp-server

meta_create_page_post

Publish a message to a Facebook Page as an immediate public post. Attach an optional link or specify a Page ID; remember the post is live instantly and can only be undone by deletion.

Instructions

Post to a Facebook Page. Immediately public — there is no draft state here, and the only undo is deleting it.

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": "meta_create_page_post"
  }
}

Input Schema

Name	Required	Description
`link`	No	A link to attach.
`message`	Yes	Post text.
`page_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description discloses critical side effects: 'Immediately public — there is no draft state here, and the only undo is deleting it.' This informs the agent that the action is irreversible and has immediate visibility consequences, which is exactly the kind of behavioral transparency needed.

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 two sentences, concise and free of extraneous detail. The key information—the action and its consequences—is presented efficiently without redundancy.

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?

The description covers the essential outcome (public post, no draft, deletion only undo) and the primary inputs (message, link, page). It does not mention any required permissions or return values, but given the simple tool and absence of output schema, this is acceptable. A slight deduction for not clarifying the purpose of page_id.

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?

The schema includes descriptions for link and message, but page_id has no description. The overall coverage is 67%, which is not high enough to assume all parameters are self-explanatory. While link and message are clearly defined, page_id's omission leaves ambiguity about its purpose and format.

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 the action: 'Post to a Facebook Page,' which is a specific verb and object. This distinguishes it from sibling tools like meta_get_page (read) or meta_create_post_comment (comment).

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies the purpose for creating a post but lacks direct 'use this when' or 'instead of' instructions. The reader must infer the appropriate context from the action name and description.

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

Deploy Server