Skip to main content
Glama
Sign In

ShortSync

by app.shortsync
OverviewDiscussionsAdmin

List scheduled posts

list_scheduled_posts
Read-only

Lists posts across the user's workspaces, defaulting to upcoming scheduled posts, soonest first. Pass status to filter by a different state, e.g. 'failed' to find posts that didn't publish, and platform to filter to one platform. Each post has id, workspace_id, platform, status, scheduled_for, video_upload_id, content_type (video, image, text or carousel), caption_preview (first line of the caption that platform posts) and, for failed posts, error_message and error_code. A failed post with duplicate_of wasn't a real failure: it was stopped because that post already went out, so don't retry it. A failed post with skipped_at_daily_limit wasn't a real failure either: a recurring occurrence had no room before its next repeat, and the series carries on. A post with moved_past_limit went past a platform's daily limit and moved to its scheduled_for on its own. Results come in pages: while next_cursor isn't null there are more posts, so call again with the same filters and cursor set to it. One upload posted to several platforms is one post per platform; pass group_by_upload: true to get one entry per upload and time with its platforms listed. Filter to one workspace by passing workspace_id; without it, all workspaces the user belongs to are searched.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of posts to return (default 20, max 100).
cursorNo`next_cursor` from the previous page. Keep the other parameters the same.
statusNoPost status to filter by: 'scheduled' (default), 'failed', 'draft', 'published', or 'ready'.
platformNoOnly posts for this platform, e.g. 'instagram' or 'snapchat'.
workspace_idNoRestrict results to one workspace. Use list_workspaces to discover valid ids.
group_by_uploadNoReturn `groups` instead of `posts`: one entry per upload and scheduled time, with the caption preview, content_type and each platform's post id and status. `limit` still counts posts, so an upload at the end of a page can continue on the next page as a second entry with the same video_upload_id and scheduled_for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "`next_cursor` from the previous page. Keep the other parameters the same.",
+  "type": "string"
+}
    • changedInput schema / properties / group_by_upload / description
      Previous value: -"Return `groups` instead of `posts`: one entry per upload and scheduled time, with the caption preview and each platform's post id and status. `limit` still counts posts."New value: +"Return `groups` instead of `posts`: one entry per upload and scheduled time, with the caption preview, content_type and each platform's post id and status. `limit` still counts posts, so an upload at the end of a page can continue on the next page as a second entry with the same video_upload_id and scheduled_for."
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Only posts for this platform, e.g. 'instagram' or 'snapchat'.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / group_by_upload
      Added value: +{
+  "description": "Return `groups` instead of `posts`: one entry per upload and scheduled time, with the caption preview and each platform's post id and status. `limit` still counts posts.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral details: default ordering, returned fields, pagination via `next_cursor`, grouping semantics, and special meanings for failed posts such as `duplicate_of`, `skipped_at_daily_limit`, and `moved_past_limit`. This is unusually transparent for a read-only listing tool and does not contradict 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.

Conciseness5/5

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

Although long, the description is front-loaded and organized around concrete tasks: default behavior, filters, returned fields, failure semantics, pagination, grouping, and workspace scope. Every section adds operational value, and there is no filler or repetition.

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 read-only, six-parameter listing tool with no output schema, the description is complete: it explains the returned post fields, pagination behavior, grouping behavior, and non-obvious failure states. An agent has enough information to call it correctly and interpret the results.

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 already 100%, so the schema documents all six parameters. The description still adds useful meaning beyond the schema, especially for `status` examples, the `group_by_upload` edge case, pagination with the same filters, and workspace scoping, though it adds little for `limit` and `cursor` beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it lists posts across the user's workspaces, defaults to upcoming scheduled posts, and orders them soonest first. The scope and default behavior are unambiguous, though it does not explicitly name sibling alternatives such as get_post_details or list_video_uploads to route between them.

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?

The description provides clear usage context: use the default for upcoming scheduled posts, pass `status` for other states such as 'failed', use `platform` to narrow by platform, and use `workspace_id` to restrict to one workspace. It gives practical when-to-use examples but does not explicitly exclude or compare this tool against sibling tools.

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

All ShortSync toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources