Skip to main content
Glama

queue-items-resolve

Resolve a queue item

Mark an item of a queue as resolved. It is the same as a check-off in the dashboard: the item leaves the pending list and a QUEUE_ITEM_COMPLETED webhook is sent. itemId is the item id or your contentId. To also take a moderation action, use POST /actions/execute.

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-resolve"
  }
}

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 resolve."New value: +"The item to resolve: 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

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, idempotent=false; the description adds genuinely useful side-effect detail — the item leaves the pending list and a QUEUE_ITEM_COMPLETED webhook fires. It does not address the non-idempotent hint (e.g. what happens on a second resolve of an already-resolved item) or whether the action is reversible via queue-items-unresolve.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and effect, then the side effect, then the parameter note, then the alternative. Four short sentences, none wasted; the itemId sentence is mildly redundant with the schema but still readable in sequence.

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?

No output schema exists, and the description compensates by explaining the observable outcome (item removed from pending, webhook emitted). It stops short of describing the response body or error behavior on an already-resolved or unknown item, which matters given idempotentHint=false.

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?

Reported schema coverage is 0% at the top level (the `request` wrapper is undocumented), but the nested properties id/itemId/projectId carry detailed schema descriptions. The description's only parameter content — itemId accepts the item `id` or your `contentId` — largely restates the schema, and it never mentions projectId, whose requiredness varies by key type.

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 ("Mark an item of a queue as resolved") and defines the effect concretely as a check-off that removes the item from the pending list. It does not, however, name the very close siblings queue-items-unresolve or queue-items-resolve-many, so an agent must infer the boundary with those from their names alone.

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?

Gives an explicit condition and alternative: if a moderation action is also wanted, use `POST /actions/execute` instead. That is real routing guidance. The missing piece is when to pick this over the bulk `queue-items-resolve-many` sibling.

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