Skip to main content
Glama

List the publishing queue

clipember_list_scheduled_posts
Read-onlyIdempotent

List posts soonest first — both clips and the user's own uploaded videos. Without a status filter it returns everything except canceled posts. Statuses: draft (saved, not queued), queued, posted, failed (see error; clipember_retry_failed_post), unconfirmed (the platform timed out after the video was sent — it may already be live; ask the user to check their profile before retrying), canceled. A queued TikTok post with hasTikTokChoice=false is waiting for a TikTok choice: the user makes it at https://clipember.com/tiktok-queue, or tells you theirs for that post and you set it with clipember_set_tiktok_choice.

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

Input Schema

NameRequiredDescriptionDefault
toNoOnly posts scheduled before this time
fromNoOnly posts scheduled at or after this time (ISO 8601) — e.g. now, to skip history
statusNoOnly these statuses, e.g. ["failed", "unconfirmed"]
connectionIdNoOnly the posts of one account (id from clipember_list_platform_connections)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / connectionId
      Added value: +{
      +  "description": "Only the posts of one account (id from clipember_list_platform_connections)",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Only posts scheduled at or after this time (ISO 8601) — e.g. now, to skip history",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Only these statuses, e.g. [\"failed\", \"unconfirmed\"]",
      +  "items": {
      +    "enum": [
      +      "draft",
      +      "queued",
      +      "posted",
      +      "failed",
      +      "canceled",
      +      "unconfirmed"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Only posts scheduled before this time",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description does add real behavioral context beyond that — result ordering, the implicit exclusion of canceled posts, the hazard around 'unconfirmed' posts possibly already being live, and the blocking TikTok-choice state — but it never explains the response shape or whether results are paginated.

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?

Front-loaded with the purpose and ordering, then dense status semantics and follow-up routing, with essentially no filler. It is long, but the length is driven by genuinely useful status disambiguation rather than restating structured fields.

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?

Covers purpose, default filtering, all status values, ordering, and escalation paths for failed/unconfirmed/TikTok-choice cases. With no output schema, it would be stronger if it said anything about what a returned post contains or whether results are bounded or paginated.

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; the description earns an extra point by giving meaning the schema's enum list does not, such as draft meaning 'saved, not queued' and unconfirmed meaning the platform timed out after sending. It also clarifies the practical effect of omitting the status filter, which the schema alone does not convey.

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?

Names a specific verb and resource (list scheduled posts), states the ordering (soonest first), and the content scope (both clips and the user's own uploaded videos). This makes it distinguishable from generic listers like clipember_list_clips without needing to open the 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?

Explicitly states the default behavior when no status filter is supplied (everything except canceled) and routes to concrete next steps: clipember_retry_failed_post for failures, clipember_set_tiktok_choice for queued TikTok posts awaiting a choice, and asking the user to verify their profile for 'unconfirmed' before retrying.

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