Skip to main content
Glama

list_queue_schedule

Read-only

List the weekly posting schedule (queue times) of each channel on this workspace: every time and the days it runs on (Everyday, Weekdays, Weekends or e.g. "Mon, Wed"), the channel's id, whether you may change it, and the time zone the times are in. Grouped by channel. platform narrows it to that platform's channels; without it, every channel is listed. This is the recurring schedule, not posts: for the next open time to queue a post, use get_queue_slots; for what is actually booked, use list_scheduled_posts. Call this before add_queue_times or remove_queue_times.

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

Input Schema

NameRequiredDescriptionDefault
platformNoOptional: only this platform's channels
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.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes beyond that by disclosing the result shape (grouped by channel, includes a per-channel editability flag and the time zone). It also clarifies the default behavior when platform is omitted (every channel is listed). The only minor gap is that it says nothing about result size or pagination for large workspaces.

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?

The return-shape enumeration is front-loaded, then filtering, then sibling disambiguation, then the sequencing advice. It is dense but every clause carries information an agent needs; nothing is repeated from the name or title.

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 must explain the return value, and it does so field by field, including grouping and time zone. Combined with the return-shape disclosure, the read-only annotations, and fully documented parameters, an agent has everything needed to call and interpret this tool correctly.

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 baseline is 3, but the description adds genuine meaning by stating that platform "narrows it to that platform's channels; without it, every channel is listed" — the omit-case behavior the enum schema does not spell out. The workspace parameter is left entirely to the schema, which handles it thoroughly, so this is a modest but real gain.

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 ("List the weekly posting schedule (queue times) of each channel on this workspace") and then enumerates the returned fields: each time, the days it runs, channel id, editability, and time zone. It explicitly distinguishes itself from get_queue_slots (next open time) and list_scheduled_posts (what is booked), so an agent can separate it from its closest siblings without opening a 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 states exactly when to reach for the alternatives (get_queue_slots for the next open time, list_scheduled_posts for booked posts) and gives a sequencing instruction: "Call this before add_queue_times or remove_queue_times." That is explicit when-to-use plus named alternatives, leaving nothing to inference.

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