Skip to main content
Glama

queue-items-unresolve

Unresolve a queue item

Mark a resolved item of a queue as pending again. It is the same as removing a check-off in the dashboard: the item comes back in the pending list. itemId is the item id or your contentId.

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": {
      "request": "<request>"
    },
    "name": "queue-items-unresolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / properties / itemId / description
      Previous value: -"The item ID to unresolve."New value: +"The item to unresolve: the item `id` from `GET /queue/{id}/items`, or the `contentId` you sent to `POST /moderate` (webhooks send it as `item.id`). For a content ID, the newest submission with that content ID is used, as the queue shows it."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent, closed-world), so the bar is lower. The description still adds real value by disclosing the observable effect — the item returns to the pending list — which is the key behavioral outcome an agent needs. It does not explain what happens if the item was never resolved, or whether an error is returned.

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 with the purpose front-loaded, followed by the effect and the parameter note. No filler, and each sentence adds distinct information.

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 simple single-operation state-change tool with rich nested schema descriptions and annotation coverage, the definition supplies enough: what it does, the resulting state, and the itemId flexibility. The only gap is that no return-value information is given, and there is no output schema to fill in.

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?

The reported schema coverage is low, so the description carries weight; it does clarify that `itemId` accepts either the item `id` or your `contentId`. However, that meaning (including the newest-submission rule and the projectId rules) is already documented more fully in the schema itself, so the description mostly restates rather than extends it.

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?

"Unresolve a queue item" is a specific verb+resource, and the body restates it precisely: "Mark a resolved item of a queue as pending again." This is clearly distinguishable from the sibling queue-items-resolve / queue-items-resolve-many tools by the inverse direction of the state change.

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?

The dashboard analogy ("the same as removing a check-off") gives a concrete sense of when this applies, but there is no explicit statement of prerequisites, when NOT to use it, or a named alternative (e.g. queue-items-resolve). Usage is implied rather than specified.

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