Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_get_scheduled_posts

Read-only

Retrieve scheduled but unpublished Facebook Page posts sorted by publish time, so you can review upcoming content before it publishes.

Instructions

List posts scheduled but not yet published, sorted by publish time (up to 500).

:param limit: Page size per Graph request (1-100, default 100). :param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fb_get_scheduled_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
page_idNo
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavior beyond that: sorting by publish time, a 500-post cap, and per-request pagination via limit. It does not explain token permission needs or error behavior, but with annotations the added context is solid.

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 purpose is front-loaded in one sentence, followed by compact per-parameter notes. There is no wasted wording or restatement of schema types.

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?

For a low-complexity list tool with annotations and an output schema, the description covers scope, ordering, result cap, pagination, and parameter defaults. The main gaps are explicit routing to sibling tools and fuller authentication context.

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 must compensate. It documents all three parameters, including limit range and default, page_id defaulting to FB_PAGE_ID, and page_access_token being optional, though the token explanation is thin.

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 states a specific verb and resource: 'List posts scheduled but not yet published, sorted by publish time.' The phrase 'scheduled but not yet published' clearly scopes the tool apart from publish-now or reschedule siblings.

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 scheduled-not-published scope implies when to use the tool, but there is no explicit when-to-use, when-not-to-use, or named alternative such as fb_get_recent_posts or fb_publish_scheduled_now.

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