Skip to main content
Glama

remove_queue_times

Destructive

Remove posting times from one channel's weekly queue schedule. Without days a time is removed from every day, like the delete button on the Posting Schedule page. Times are 24-hour HH:MM in the workspace's posting time zone. 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>"
    },
    "name": "remove_queue_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional: only these days (day names, or everyday, weekdays, weekends). Omit for every day.
timesYesTimes to remove, 24-hour HH:MM
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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to argue that this mutates. It adds genuinely useful scope detail beyond the annotations: omitting `days` wipes the time from every day, and already-queued posts retain their times. It does not say whether the removal is reversible or confirmable.

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?

Four short sentences, front-loaded with the verb and scope, then the side-effect caveat. Every sentence carries information an agent would otherwise have to guess.

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 the operation's scope, the destructive breadth of the all-days case, and the effect on existing queued posts. Minor gaps remain for a mutation tool: what happens when a supplied time is not in the schedule, and whether any confirmation or return value is produced.

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 baseline is 3. The description still adds value by pinning `times` to 24-hour HH:MM evaluated in the workspace's posting time zone, and clarifying that an omitted `days` means every day – timezone semantics are not in the schema.

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?

States a specific verb and resource with clear scope: 'Remove posting times from one channel's weekly queue schedule.' It is easy to tell apart from add_queue_times, though the sibling is not named explicitly.

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?

Explains the `days`-omitted behavior and analogizes to the Posting Schedule delete button, which gives implied usage context. It gives no explicit guidance on when to use this versus related tools such as add_queue_times, pause_queue, or list_queue_schedule to inspect the current schedule first.

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