CatchAll

List User Jobs

list_user_jobs

List all jobs submitted by you.

Returns your job history with IDs, queries, statuses, and timestamps.

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

Input Schema

Name	Required	Description
`mode`	No	Optional filter by job processing mode: 'base' or 'lite'.
`page`	No	Page number for pagination (default: 1)
`search`	No	Optional text filter on the job query.
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`ownership`	No	Optional ownership filter: 'all', 'own', or 'shared'.
`page_size`	No	Number of results per page (default: 100, max: 1000)
`project_id`	No	Optional filter to jobs belonging to a specific project.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 13, 2026

addedInput schema / properties / mode

Added value: +{
+  "default": "",
+  "description": "Optional filter by job processing mode: 'base' or 'lite'.",
+  "type": "string"
+}

First observedJul 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It accurately states that this is a list/read operation and describes the returned data fields. It does not mention pagination behavior or authentication requirements, and it does not explicitly assert read-only safety, though the verb 'List' makes it reasonably evident.

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?

The description is two short sentences with no filler. The main action is front-loaded, and the return fields are listed efficiently. Every sentence adds useful information.

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?

With an output schema present, all parameters optional, and 100% schema coverage, an agent can invoke this tool without additional guidance. The description covers scope and return fields. Minor gaps include not mentioning pagination defaults or how this differs from monitor-job listing, but these are largely covered by the schema and output 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 description coverage is 100%, so the parameter schema fully documents all seven optional parameters. The description adds no parameter-specific meaning beyond what the schema already provides, earning the baseline score of 3.

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 uses a specific verb ('List') and resource ('jobs submitted by you') and enumerates the returned fields. It clearly indicates user-owned job history, distinguishing it from single-job status retrieval, though it does not explicitly reference sibling tools.

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 intended context is implied: use when you need your own job history. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like list_monitor_jobs or get_job_status. Some usage context is present, but the description does not actively route the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CatchAll tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.