Skip to main content
Glama

Mark a queued video done

mark_queue_done
Idempotent

Closes one entry in the user's queue, given its queue_id. The video stays in the user's library; only the queue entry is closed.

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": {
      "queue_id": "<queue_id>"
    },
    "name": "mark_queue_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
queue_idYes

Output Schema

NameRequiredDescriptionDefault
doneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare non-read-only, idempotent, and non-destructive, and the description adds genuinely useful context beyond them: the video remains in the user's library and only the queue entry is closed. It does not cover what happens with an invalid or already-closed queue_id, which keeps it from a 5.

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?

Two short sentences, the operation front-loaded and the important scope clarification immediately after. Nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile for this simple single-parameter mutation. The main remaining gap is guidance on obtaining a valid queue_id and behavior on a missing entry.

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?

Schema description coverage is 0%, so the description carries the burden for queue_id, yet it only restates that the call is 'given its queue_id' with no indication of where the ID comes from (e.g., get_my_queue) or its format. This is essentially a repeat of the required-field schema.

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?

The description gives a specific verb and resource ('Closes one entry in the user's queue') plus the key selector (queue_id), which clearly separates it from library-wide tools like search_my_library or list_my_saves. It does not explicitly name a sibling alternative, so it falls short of a 5.

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?

Usage is implied by the verb: use this to close a queue entry. There is no explicit statement of when not to use it (e.g., removing a saved video, or cancelling something outside the queue) and no named alternative for related operations.

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.