Publish an immediate Facebook Page post with text, an optional link, or a picture attachment. Use it to share updates directly to a Page.
Create and publish an immediate post on the Facebook Page. Supports text, link, and picture attachments.
| Name | Required | Description | Default |
|---|---|---|---|
| link | No | Optional URL to attach to the post | |
| message | Yes | The text content of the post | |
| picture | No | Optional image URL to attach to the post |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose the meaningful trait that publishing happens immediately (a public, hard-to-reverse side effect) versus scheduling, but says nothing about required Page permissions, rate limits, or whether the post can be retracted afterward.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, both earning their place, with the core purpose and immediate-publish constraint front-loaded before the attachment list.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a small 3-parameter tool with no output schema and no annotations, the essentials are present, but the description omits auth expectations and what a successful publish yields (e.g., a post ID), which an agent would benefit from knowing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents message, link, and picture. The description's mention of 'text, link, and picture attachments' merely restates those fields without adding format or constraint detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (create/publish) and resource (post on the Facebook Page) plus the supported content types. The word 'immediate' implicitly separates it from the scheduler sibling, but no sibling is named explicitly, so it falls just short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: 'immediate' hints that this is the non-scheduled path versus facebook_schedule_post, but the description never states when to choose this over that sibling or what prerequisites apply. No exclusions or alternatives are spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.