Skip to main content
Glama

add_queue_times

Add posting times to one channel's weekly queue schedule. Times are 24-hour HH:MM in the workspace's posting time zone (list_queue_schedule names it). A time already on the schedule is left as it is. Posts already queued keep their times.

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": {
      "platform": "<platform>",
      "times": "<times>",
      "days": "<days>"
    },
    "name": "add_queue_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesDays the times run on: day names (monday...sunday) or one of everyday, weekdays, weekends
timesYesTimes to add, 24-hour HH:MM, e.g. ["09:00", "14:30"]
platformYesThe channel's platform
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.
platform_account_idsNoWhich channel, when the platform has more than one: {platform: id}, ids from list_queue_schedule

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

A3.9/5.0
Behavior4/5

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

Beyond the annotations, which already flag a non-read-only but non-destructive mutation, the description adds real behavioral facts: duplicate times are idempotent ('left as it is') and already-queued posts keep their assigned times. That tells the agent the call will not disturb existing content, which the annotations alone cannot convey. It stops short of saying what permissions are needed or what the call returns.

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?

Three short sentences, front-loaded with the purpose, then the format/time-zone rule, then the two idempotency guarantees. Nothing is redundant and each sentence contributes a distinct fact.

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?

For a five-parameter mutation tool with a fully described schema and no output schema, the description covers the critical ambiguities: time format, time zone source, duplicate handling, and effect on existing queued posts. The remaining gap is that it never states what the caller gets back or whether an error occurs for malformed times or days.

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 parameter descriptions already document days, times, platform, workspace, and platform_account_ids. The description still adds meaning the schema lacks, namely that times are interpreted in the workspace's posting time zone, with list_queue_schedule pointed to as the source of that zone. The 'one channel' phrasing also clarifies the role of platform_account_ids in multi-account cases.

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 opens with a specific verb and resource: 'Add posting times to one channel's weekly queue schedule.' That clearly separates it from post-level tools like queue_post and schedule_post. It does not explicitly contrast itself with remove_queue_times, but 'add' versus 'remove' leaves no real ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this configures the recurring queue rather than scheduling a single post. There is no explicit statement of when to use this tool versus queue_post, schedule_post, or get_best_time_to_post, and no stated prerequisites such as whether the queue must be paused or active.

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