mcp-kaggle-tool

kaggle_run_notebook

Execute a Kaggle notebook programmatically by providing its slug identifier. Automate notebook runs without manual login.

Instructions

Run/execute a Kaggle notebook

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": {
      "kernelSlug": "<kernelSlug>"
    },
    "name": "kaggle_run_notebook"
  }
}

Input Schema

Name	Required	Description	Default
`kernelSlug`	Yes	Notebook identifier (username/notebook-slug)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations are present, and the description fails to disclose key behaviors such as whether the execution is synchronous or asynchronous, what side effects occur, or what triggers are needed. The agent gains no behavioral insight beyond the verb 'run'.

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?

The description is extremely brief (one short phrase) and front-loaded, but it is not a complete sentence. It avoids unnecessary words, yet could be slightly more verbose to improve clarity without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is insufficient. It does not explain return values, execution behavior, or prerequisites, leaving the agent underinformed for a tool that likely involves non-trivial side effects.

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 single parameter 'kernelSlug' has a description in the schema that already explains it is a notebook identifier. The description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 the action (run/execute) and the resource (Kaggle notebook). It is distinct from sibling tools like create, get status, or list, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., kaggle_get_notebook_status for checking completion). The agent must infer usage from context alone.

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

Deploy Server