Skip to main content
Glama

Candidate emotional moments waiting for a human eye

get_clip_queue
Read-only

Moments found automatically in checked interviews (pauses after strong lines) that may be emotional reactions. Each has a YouTube link a few seconds before the moment and the votes so far. Watch the listener and vote with POST /api/v1/clips/queue/{id}/vote {reaction: true|false}; confirmed moments become clips.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 openWorldHint=false, and the description adds real context on top: results are auto-generated candidates, each carries a YouTube link offset a few seconds before the moment and the current vote tally, and confirmed moments become clips. That is meaningful disclosure about data shape and downstream effect. It omits ordering, freshness, and whether the queue excludes already-voted items.

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?

Two sentences, front-loaded with the resource definition before the follow-up action guidance; there is little waste. The phrasing 'that may be emotional reactions' is slightly redundant with the title but harmless.

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 does well to enumerate the fields per item (link, votes) and the confirmation path. It is still incomplete for a paginated queue: no ordering, no default limit, no indication of volume or what 'checked interviews' scopes, which an agent needs to call it 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 single parameter (limit, 1-100) has 0% schema description coverage, and the description never mentions it, its default, or how results are ordered or truncated. With an undocumented parameter the description had to compensate and does not, leaving an agent to guess at result-set size behavior.

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 names the resource concretely: automatically detected moments in checked interviews (pauses after strong lines) that may be emotional reactions, plus what each entry contains. An agent can tell this returns a review queue rather than finished clips. It falls short of 5 because it never distinguishes itself from similarly named siblings such as find_clip_candidates or get_clips.

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 through the workflow: watch the listener, then vote via POST /api/v1/clips/queue/{id}/vote with {reaction: true|false}. That tells the agent what to do with results, but there is no explicit statement of when to call this versus find_clip_candidates or get_clips, and no prerequisites or exclusions.

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.