Skip to main content
Glama

List scheduled posts

klynx_list_scheduled_posts
Read-onlyIdempotent

Use this when the user asks what is queued to post, or before cancelling a scheduled post. Returns each post waiting to publish on a connected Facebook Page or Instagram account: schedule_id, post_id, account_id, account name, platform, status (scheduled or publishing), scheduled_for, timezone, the start of the caption and the image URL. Free, takes no inputs and changes nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
scheduled_postsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds value beyond them by stating 'Free', 'takes no inputs' and 'changes nothing' — cost and side-effect context the annotations do not carry. What it omits is paging/limit behavior for potentially long queues.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the usage trigger before the return contract. The field enumeration is somewhat redundant with the existing output schema, but it is compact and does not obscure the main point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only listing tool with full annotations and an output schema, the description covers when to call it, cost, side effects, and the shape of the result. Nothing an agent needs in order to invoke it correctly is missing.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description reinforces this by stating 'takes no inputs', so the agent knows no filtering by account or platform is possible here.

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 gives a specific verb and resource ('List scheduled posts' / 'each post waiting to publish') plus the scope: only connected Facebook Pages and Instagram accounts. It enumerates the returned fields including the status values ('scheduled or publishing'), so an agent can tell exactly what this returns without opening the output schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies two concrete triggers: 'when the user asks what is queued to post' and 'before cancelling a scheduled post', which implicitly routes to the klynx_cancel_scheduled_post sibling. There is no explicit when-not or negative routing (e.g. how to see already-published posts), so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources