Skip to main content
Glama

queue_post

Add a post to the next available queue slot. Uses your configured posting schedule. A channel with no posting times is refused and nothing is added for it: add some with add_queue_times first. When the account has multiple connected accounts for a platform, pass platform_account_ids to target a specific one; otherwise the first connected account is used. If the next slot is within 15 minutes of now, nothing is queued: the reply carries a link the user must open to confirm it. Show the user the link; don't try to confirm it yourself.

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": {
      "id": "<id>"
    },
    "name": "queue_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID to queue
platformsNoPlatforms (defaults to post's existing platforms). Instagram needs an image or video on the post: if it has none, add one with `update_draft` (`images`) first.
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.
variance_minutesNoOptional override for the account's posting-time variance window, 0-60. The stored time is jittered by up to half of it. 0 stores the exact slot time.
platform_account_idsNoOptional map of platform => connected_account_id (numeric id from `list_connected_accounts`). Each id must belong to the current account and match the platform.

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.4/5.0
Behavior5/5

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

The description discloses important behavior beyond the annotations: channels without posting times are refused and nothing is added, the first connected account is used unless platform_account_ids is supplied, and near-term slots are not queued but instead require the user to open a confirmation link. It also explicitly instructs the agent not to confirm the link itself.

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 description is front-loaded with the primary action and then adds necessary constraints. It is reasonably efficient, though some sentences could be tightened without losing meaning.

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 multi-parameter scheduling tool with full schema coverage and no output schema, the description covers the important operational context: scheduling prerequisites, account selection, near-term confirmation behavior, and the user-facing confirmation link. Nothing critical for correct invocation appears missing.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all five parameters thoroughly. The description adds useful meaning for platform_account_ids by explaining the default first-account behavior, but it does not add much beyond the schema for id, platforms, workspace, or variance_minutes.

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 states a specific verb and resource: add a post to the next available queue slot using the configured posting schedule. This distinguishes it implicitly from schedule_post and publish_post by emphasizing the next available slot rather than a fixed time or immediate publishing, though it does not name those siblings explicitly.

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 explicitly covers when the tool can be used, what happens when a channel has no posting times, and directs the user to add_queue_times first. It also explains when to pass platform_account_ids and what to do when the next slot is within 15 minutes, including showing the confirmation link to the user rather than confirming it directly.

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