Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_reschedule_post

Changes the publish time of a scheduled Facebook post or video by setting a new UNIX timestamp at least 10 minutes in the future.

Instructions

Change the publish time of a scheduled post or video.

:param post_id: Id of the scheduled post/video. :param new_scheduled_time_unix: New time, UNIX seconds, at least 10 minutes ahead. :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>",
      "new_scheduled_time_unix": "<new_scheduled_time_unix>"
    },
    "name": "fb_reschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
page_access_tokenNo
new_scheduled_time_unixYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds one genuinely new behavioral constraint not in structured data — the new time must be at least 10 minutes ahead — but says nothing about required post state, permission needs, or failure modes when the window is violated.

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?

One summary sentence front-loads the purpose, followed by a short parameter block with no filler. Every line adds information an agent needs given the empty schema descriptions.

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, and all three parameters are documented. The remaining gap is behavioral edge cases — whether the post must still be in scheduled state and what error surfaces inside the 10-minute window — for what is otherwise a simple three-parameter mutation.

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 description coverage is 0%, so the description carries the burden, and it does: post_id is identified as the scheduled post/video id, new_scheduled_time_unix is clarified as UNIX seconds with a minimum lead time, and page_access_token is marked optional. It could add more on token scope (which page's token) but covers all three parameters meaningfully.

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 and resource ('Change the publish time of a scheduled post or video'), which is unambiguous and distinct from publishing or deleting a post. It does not explicitly name a sibling such as fb_publish_scheduled_now, so it stops short of full sibling differentiation.

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?

Usage is only implied via the operation name and the 'at least 10 minutes ahead' precondition; there is no explicit statement of when to choose this over fb_publish_scheduled_now or fb_publish_post, nor what happens if the post is already published or outside the window.

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