Skip to main content
Glama

resume_queue

Undo pause_queue: publishing starts again for the whole account. Scheduled and queued posts keep their times. If the queue isn't paused it says so and changes nothing. The reply says how many scheduled posts will go out.

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

Input Schema

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

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that scheduled and queued posts keep their times, that a no-op path exists when the queue isn't paused, and that the reply reports how many scheduled posts will go out. That is exactly the mutation-safety context an agent needs before calling.

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 action and its inverse, then effects, then the no-op edge case, then the response. No filler and nothing redundant.

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?

With no output schema, the description helpfully summarizes the reply (count of scheduled posts) and covers the no-op case, so an agent can call it correctly. The only gap is whether resuming is account-wide or scoped by the workspace parameter, which the 'whole account' phrasing muddies rather than resolves.

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% and the single optional workspace parameter is fully documented there, including the list_workspaces/select_workspace cross-references. The description adds no parameter-level detail and even says 'whole account', which leaves a slight ambiguity about how the workspace parameter interacts with the resume scope.

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?

States a specific action and its inverse relationship: 'Undo pause_queue: publishing starts again for the whole account.' The scope (whole account) and the sibling it reverses are both explicit, so an agent can distinguish it from pause_queue immediately.

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

Usage Guidelines4/5

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

Usage is clearly implied by naming pause_queue as the thing being undone, and the description adds a when-not case ('If the queue isn't paused it says so and changes nothing'). It stops short of naming any other alternative or stating prerequisites, but the selection context is unambiguous.

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