Skip to main content
Glama

OpenShorts.io

List recent clipping jobs

list_jobs

The most recent jobs on this account, newest first.

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": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states ordering and account scoping, but says nothing about read-only safety, whether results are truncated, what a job record contains, or any auth requirements.

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?

A single short sentence with the scoping and ordering facts front-loaded and no filler. It is efficient, though the brevity comes partly from omitting information the tool needs.

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?

This is a simple read-only listing with one optional parameter and no output schema, so heavy explanation is not required. Still, the description never addresses the limit cap, the result shape, or how this differs from get_job, leaving an agent to infer those from context.

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

Parameters3/5

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

The description does not mention the single limit parameter at all, leaving its semantics to the schema, which already supplies a default of 10 and a range of 1-30. The name is self-explanatory, so this is a minor gap rather than a blocking one, but no meaning is added beyond the 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 names the resource (jobs) and its scope (most recent, on this account) and states the ordering (newest first), so an agent can tell it retrieves a job listing. It stops short of an explicit verb and never contrasts itself with get_job, which is why it does not reach 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Most recent' implies a recency-driven use case but there is no explicit when-to-use statement and no exclusion. Nothing tells the agent to prefer get_job when it already has an ID, or get_usage when it wants quota data.

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