Skip to main content
Glama

Your recent generations

list_my_jobs
Read-onlyIdempotent

Your recent image, video and character jobs, newest first, with status and errors. Use get_job for results. Page with nextCursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive behavior, so the description only needs to add operational context, which it does: newest-first ordering, inclusion of status and errors, and cursor-based paging. It does not mention the default page size of 20 or the 50 cap, though those are visible as schema constraints.

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?

Three short sentences with no filler: scope and contents first, the disambiguation second, pagination last. Every clause carries information an agent needs before calling.

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?

There is no output schema, so the description usefully states what comes back (status and errors, newest first) and how to continue paging. For a two-parameter read-only list tool this is nearly complete; only page-size behavior is left implicit in the schema.

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?

Schema coverage is 0%, so the description must carry parameter meaning. "Page with nextCursor" conveys that the cursor parameter drives paging, but it uses the output field name rather than the actual `cursor` parameter and says nothing about what `limit` controls beyond the schema's own default and maximum.

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?

The description names the resource (image, video and character jobs), the scope (yours, recent), the ordering (newest first), and what each entry carries (status and errors). It also explicitly separates this from get_job, so an agent can tell the list view from the detail view without inspecting either schema.

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

Usage Guidelines4/5

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

"Use get_job for results" gives a clear routing rule to the main competing tool: list here, fetch details there. It stops short of exclusions against other list_* siblings, but the job-scoped framing makes the intended use unambiguous.

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