Skip to main content
Glama

cleanup_job

Deletes a finished Kaggle job's kernel, outputs, and per-job dataset to free resources and remove stored artifacts.

Instructions

Delete a finished job's kernel (with its outputs) and per-job dataset from Kaggle.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it clearly discloses the destructive scope (kernel, outputs, per-job dataset). However, it omits irreversibility, required permissions, behavior when the job is not finished, and whether the operation is idempotent.

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 a single front-loaded sentence that identifies the action and exactly what gets deleted. Every phrase contributes scope or prerequisite information, with no filler.

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?

The output schema is present, so return values need not be explained. For a destructive no-annotation tool, the description covers what is deleted but leaves out operational details such as irreversibility, error behavior, and permissions that an agent would need before invoking it.

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% for the single job_id parameter, so the schema only supplies the name and string type. The description adds the meaningful constraint that the job must be finished, but it does not clarify job_id format, source, or validation.

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 ("Delete") and names two concrete resources: the finished job's kernel with outputs and the per-job dataset. It implicitly distinguishes the per-job dataset from user datasets handled by delete_dataset, but does not explicitly compare itself to any sibling.

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 "finished job's" implies a prerequisite that the job must be complete before cleanup, but the description does not state when to use this versus delete_dataset or other cleanup alternatives. Usage is implied rather than explicitly guided.

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