Skip to main content
Glama

queue-items-resolve-many

Resolve queue items

Mark up to 100 items of a queue as resolved in one request. Each item is resolved the same as with POST /queue/{id}/items/{itemId}/resolve, and each ID is an item id or your contentId. IDs that match no item in the project are skipped and returned in notFoundIds.

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

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / properties / body / properties / itemIds / description
      Previous value: -"The item IDs to resolve. Up to 100."New value: +"The items to resolve, up to 100. Each is 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.4/5.0
Behavior4/5

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

Annotations only declare the coarse profile (not read-only, not destructive, not idempotent, open-world); the description adds real operational detail beyond that: the 100-item cap, the fact that unmatched IDs are silently skipped rather than erroring, and that they come back in `notFoundIds`. It leaves open what happens to items already in a resolved state, which matters given idempotentHint=false.

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 sentences, each carrying distinct information: what the tool does, the size limit, per-item equivalence to the single endpoint, and the not-found behavior. The batch limit is front-loaded and there is no filler.

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 mutation tool with a single nested request object, no output schema and no annotations detail, the description covers the essential behaviors including the partial-success return (`notFoundIds`). It is not fully complete on edge cases (already-resolved items, permission requirements for the project) but nothing critical to a correct call is missing.

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?

Although the reported schema description coverage is 0%, the description itself explains that each entry in `itemIds` may be either an item `id` or a `contentId`, and that content IDs resolve to the newest submission as shown in the queue. That is the key semantic an agent needs and it is not inferable from a plain string array; project scoping is left entirely to the schema.

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 verb and resource ('Resolve queue items') and immediately scopes it as a bulk operation ('Mark up to 100 items of a queue as resolved in one request'), which is exactly what separates it from the sibling queue-items-resolve. An agent can pick between the batch and single-item tools without opening either schema.

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?

It gives a clear condition for choosing this tool (multiple items, up to 100, in one request) and anchors the per-item semantics to the known single-item endpoint `POST /queue/{id}/items/{itemId}/resolve`. It does not state when not to use it (e.g., for a single item, or that unresolve is the inverse), so the routing is strong but not exhaustive.

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