Skip to main content
Glama

list_scheduled_posts

Read-onlyIdempotent

List the posts in a workspace — the content queue.

status filters to any of "draft", "scheduled", "published", "failed"; omit it for everything. since/until are ISO datetimes bounding when a post published (or, if it hasn't, when it is scheduled to). mode filters to one kind — "reel", "post", "carousel" or "story" — e.g. mode="story" for the queued stories; each row says which kind it is. A story has no caption.

Use this to answer "what's going out this week", to find a post's id before update_scheduled_post or cancel_scheduled_post, and to get a published post's ig_media_id for targeting an automation. For how posts performed use the analytics tools instead — this returns the queue, not metrics.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_scheduled_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
sinceNo
untilNo
statusNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond them: each row self-identifies its kind, stories have no caption, and since/until bound publish time or, for unpublished posts, scheduled time. It does not mention result volume, pagination, or ordering, which keeps it off 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 tight paragraphs with the identity sentence front-loaded, filters second, task routing last. Every sentence adds information; the closing "returns the queue, not metrics" reinforces rather than repeats the exclusion.

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?

With an output schema present the description needn't explain return shape, and annotations cover safety, so the remaining burden is filter semantics and routing — both handled well. The notable gap is ordering and any result cap on the listing, which an agent may care about when sweeping a queue.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and no enums are declared, so the description carries the full burden — and does: it enumerates acceptable `status` values, lists `mode` values ("reel", "post", "carousel", "story") with an example, explains omitting `status` returns everything, and defines the temporal semantics of `since`/`until`. Only `workspace_id` and timezone assumptions go unstated.

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?

Opens with a specific verb+resource and a clarifying gloss: "List the posts in a workspace — the content queue." It also explicitly distances itself from the analytics tools ("this returns the queue, not metrics"), so an agent can separate it from get_account_analytics / get_analytics_summary without reading schemas.

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?

Gives concrete use cases ("what's going out this week", finding a post's `id` before update_scheduled_post or cancel_scheduled_post, getting `ig_media_id` for an automation) and an explicit exclusion routing to analytics tools for performance data. Both when-to-use and when-not-to-use are stated.

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