Skip to main content
Glama
SutariH

postapop-demo

by SutariH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List scheduled posts

list_scheduled_posts
Read-only

List posts in a social media calendar by status and date window to see what is scheduled, published, or still a draft. Use it to look up channel ids before creating a draft.

Instructions

Lists posts in the workspace's social media calendar. Use it to answer questions such as "What is scheduled next week?" or "What did we publish this month?", and to look up channel ids before you call create_draft_post. status "upcoming" (the default) returns scheduled posts, "published" returns posts that went out, and "drafts" returns drafts that have no time yet. Without from and to, upcoming covers the next 14 days and published covers the last 14 days. A window can be at most 31 days long. Drafts ignore from and to. Times in the result are UTC. Convert them to the workspace time zone, which the result also gives, when you talk to the user. This tool only reads. It never changes, schedules or publishes a post.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the time window (not included), ISO 8601 with an offset.
fromNoStart of the time window, ISO 8601 with an offset, for example 2026-11-02T00:00:00-05:00.
statusNoWhich posts to list.upcoming

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding behavior annotations don't capture: the 31-day maximum window, 14-day default ranges per status, the fact that 'to' is exclusive, that drafts ignore the window, and that result times are UTC against a workspace time zone included in the response. That is substantial added context beyond the structured fields.

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?

Front-loaded with purpose and the questions it answers, then rules ordered by likely need (status modes, defaults, window cap, drafts, time zone, read-only reassurance). Every sentence carries a distinct constraint or instruction with no filler.

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 still tells the agent what the result contains (UTC timestamps plus the workspace time zone) and instructs it to convert before speaking to the user. Combined with default ranges and the 31-day cap, nothing needed to call this correctly is missing.

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 100%, but the schema's status description is only "Which posts to list," and the description goes well beyond it by defining upcoming/published/drafts and their default date ranges. It also clarifies the from/to window limit and that drafts ignore both parameters, adding real semantics the schema does not carry.

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 plus scope: "Lists posts in the workspace's social media calendar." It also distinguishes itself from the sibling create_draft_post (read-only lookup of channel ids for that call), so an agent can route without opening either 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 concrete question patterns the tool answers ("What is scheduled next week?"), explains each status mode's meaning, states the default windows for upcoming vs published when from/to are omitted, and notes that drafts ignore from/to. It also states the key when-not boundary: this tool never changes, schedules or publishes a post.

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

Deploy Server

Other Tools