Skip to main content
Glama

list_scheduled_posts

Read-only

Answer "what's going out today?", "what's scheduled this week?", "what's coming up?". Lists scheduled posts in the order they next go out, each with its id, time, channel and the start of its copy. Times are in the workspace's posting time zone, which each time names. Every window starts with any post that missed its time, oldest first, with the reason. today is the workspace's calendar day (up to 10 posts), week is the next 7 days (up to 15), upcoming is everything ahead (up to 10, the default). If there is nothing, it says so. No performance numbers. For drafts, use list_drafts. For the open times in the weekly schedule, use get_queue_slots.

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

Input Schema

NameRequiredDescriptionDefault
windowNotoday, this week, or everything upcoming. Default upcoming.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, non-destructive, closed-world), so the description carries the behavioral weight and does: result ordering by next send time, the fields returned, workspace-time-zone semantics with the zone named on each time, missed-post surfacing with reasons at the head of every window, the empty-result behavior, and an explicit exclusion ("No performance numbers"). These are traits an agent cannot infer from the annotations.

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?

The tool is front-loaded with concrete user questions before any mechanics, and nearly every sentence conveys a distinct rule. There is minor redundancy in restating the default window and the per-window caps that the schema's enum description already hints at, which keeps it just shy of a 5.

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?

With no output schema, the description must describe returns, and it does: the returned fields, the ordering, the time-zone labeling, and the missed-post preamble. For a two-parameter read tool whose annotations cover safety, nothing an agent needs to call it correctly is absent.

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 coverage is 100%, so the baseline is 3, and the description earns above that by attaching per-value limits, the definition of "today" as the workspace's calendar day, and which value is the default — meaning that goes beyond the enum's own labels. The workspace parameter's per-call, non-persistent nature is reinforced in the schema already, so that part is not new information.

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 opens with a specific verb and resource in the user's own phrasing ("what's going out today?") and then states plainly that it "lists scheduled posts in the order they next go out." It explicitly names the two nearest siblings it is not — list_drafts for drafts and get_queue_slots for open queue times — so the agent can separate it from the rest of the list_* family without opening a schema.

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

Usage Guidelines5/5

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

It gives the exact question patterns that should route here, defines each window's span and cap (today up to 10, week = next 7 days up to 15, upcoming up to 10 and the default), and names alternatives for adjacent intents (drafts, queue slots). Both when-to-use and when-to-look-elsewhere are covered.

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