Skip to main content
Glama

Get my queue

get_my_queue
Read-onlyIdempotent

Lists the videos the user sent from the SavedThat app with its 'Send to' button, newest first: title, channel, url, the moment they picked (at_seconds), a deep link to that second and a queue_id for each entry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the strict scope (only items sent via the app's Send to button) and the newest-first ordering. It stops short of saying anything about the limit/pagination behavior or what happens when the queue is empty.

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?

A single front-loaded sentence with the resource and scope first, then a compact colon-delimited field list. Nothing is redundant and no sentence needs to be removed.

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 enumerating return fields is a bonus rather than a requirement, and the annotations fully cover the read-only nature of the call. The only meaningful gap is the unmentioned limit parameter and its paging implication.

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% and the single parameter (limit, default 10, max 50) is never mentioned in the description. Only the schema's default/maximum hints at its meaning, so the description does not compensate for the coverage gap; it simply ignores the parameter.

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 ('Lists') and resource ('the videos the user sent from the SavedThat app with its Send to button'), plus the ordering ('newest first') and the exact fields returned. The 'Send to' origin distinguishes this queue from saved-library siblings like list_my_saves without needing to name them.

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 only implied: an agent can infer this is the tool for viewing items queued via the Send to button. There is no explicit when-to-use/when-not guidance, no mention of how it relates to mark_queue_done or list_my_saves, and no stated prerequisites.

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.