Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_publish_scheduled_now

Publish a scheduled Facebook Page post immediately instead of waiting for its scheduled time. Confirm first because this action is public.

Instructions

Publish a scheduled post immediately. This is public: confirm first.

:param post_id: Id of the scheduled post. :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": {
      "post_id": "<post_id>"
    },
    "name": "fb_publish_scheduled_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations cover the safety profile (not read-only, open-world, non-idempotent, not destructive), so this description only needs to add context. It does: 'This is public: confirm first' discloses external visibility and a confirmation requirement that no annotation conveys. It omits the double-publish / non-idempotency risk and what happens to the scheduled entry afterwards, which keeps it below a 5.

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?

Three short lines with the action stated first and the confirmation warning immediately after, before the parameter notes. Nothing is padded except the 'Optional Page token' line, which earns its place because the schema leaves the parameter undocumented.

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?

An output schema exists, so return values need not be explained. Given a two-parameter, single-action tool, the description covers the action, the public side effect, and both parameters; only edge cases (post not actually scheduled, missing permissions) are absent.

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 0%, so the description must carry the semantics, and it does at a minimal level: post_id is the ID of the scheduled post and page_access_token is optional. It adds no format expectations, no indication of which token scopes are required, and no consequence if the optional token is omitted.

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?

States a specific verb+resource combination ('Publish a scheduled post immediately'), which is meaningfully distinct from the reschedule and generic publish siblings. It does not explicitly name an alternative, but the immediacy/scope qualifier makes the operation identifiable on its own.

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 implies when to use it (for an already-scheduled post rather than a new one) and adds a precondition to confirm because the result is public. It never states when to prefer fb_publish_post or fb_reschedule_post instead, leaving the choice between siblings to inference.

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