Skip to main content
Glama

queue-items-list

Read-only

List queue items

List the items of a review queue, with the filters and the date window of the queue applied. By default only pending items. The list is paginated. Use the item id or contentId to resolve or unresolve an item.

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

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real behavior: pending-only default, queue-level filters and date window applied automatically, and pagination. It stops short of describing page-size limits, ordering semantics of the sort enum, or what an empty/oversized page looks like.

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?

Short and front-loaded: the core action leads, followed by filtering, default, pagination, and the sibling hint in that order. The first line merely restates the title before the real sentence begins, a minor redundancy, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry return-value information, and it only says the list is paginated without describing the item shape or what fields come back. Combined with the near-empty parameter documentation on a twelve-field nested request, the definition is adequate to call the tool but not complete for using its filters correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The nested request object carries roughly a dozen sub-parameters and only `id` and `projectId` have schema descriptions, so coverage is very low and the description must compensate. It only hints at two of them — the date window (afterDate/beforeDate) and the pending default (includeResolved) — and says nothing about page, pageSize, sort, labels, authorId, conversationIds, or filteredActionIds.

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 ("List the items of a review queue") and scopes it with "with the filters and the date window of the queue applied," which separates it from queue-list and queue-get-stats. The closing sentence implicitly points at queue-items-resolve/unresolve by telling the agent to use an item `id` or `contentId` for those actions, but no sibling is 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?

Gives one important usage fact — the default result set is pending items only — and steers resolution work elsewhere via the `id`/`contentId` note. It never states when to choose this over queue-list or queue-get-stats, nor when to set includeResolved versus calling a different tool, so selection among siblings is left to inference.

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