Skip to main content
Glama

TranscriptLab

List job items

transcriptlab_list_job_items
Read-only

Return per-video results for a batch or channel job. App-facing only. Page with the returned cursor.

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": {
      "job_id": "<job_id>"
    },
    "name": "transcriptlab_list_job_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the read-only, non-destructive, open-world profile, so the bar is lower. The description adds pagination behavior ('page with the returned cursor') and an 'App-facing only' scope note, but leaves ordering, page termination, and result fields unexplained, and 'App-facing only' is left ambiguous.

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?

Three short, front-loaded sentences with no filler; the pagination directive comes before any detail. The terse 'App-facing only' fragment costs some clarity but wastes no words.

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 should convey the shape of returned items; 'per-video results' is directionally useful but says nothing about fields, ordering, or what an empty page looks like. Adequate for locating the tool, thin for invoking it confidently.

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% across three parameters, so the description carries full burden. It only loosely gestures at job_id and cursor; the limit parameter (1-100) is never mentioned and the cursor's opacity/origin is only partially implied.

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: return per-video results for a batch or channel job. This implicitly separates it from status-oriented siblings like transcriptlab_get_job_status, though no sibling is named.

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?

The phrase 'for a batch or channel job' implies the prerequisite (a job must exist) and 'App-facing only' hints at a caller restriction, but no explicit when-to-use versus get_job_status or list_transcripts is given, and no when-not guidance.

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.