CatchAll (by NewsCatcher)

Official

by Newscatcher

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_job

Permanently delete a job and its associated results from your account. Use this to clean up jobs you no longer need.

Instructions

Permanently delete a job and its results.

Use when:

You want to remove a job you no longer need from your account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	The job ID to delete.
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses permanence and that results are also deleted, which is key for a deletion tool. However, it could mention prerequisites or state changes.

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 extremely concise: two sentences with a bullet for usage. Every word serves a purpose with no redundancy.

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?

Given the tool's simplicity (2 params, 1 required, output schema exists), the description is sufficiently complete. It covers purpose and usage, though slightly more behavioral detail could be added.

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 adds no extra meaning beyond the input schema, which already describes both parameters. Schema description coverage is 100%, so baseline score of 3 is appropriate.

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 clearly states it permanently deletes a job and its results, using a specific verb and resource. It distinguishes from sibling delete tools (e.g., delete_dataset, delete_entity) by explicitly mentioning 'job'.

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?

The 'Use when' section provides clear context for when to use the tool: to remove a job no longer needed. It does not explicitly state when not to use, but the context is sufficient.

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

Deploy Server