mcp-kaggle-tool

kaggle_list_notebooks

Retrieve a paginated list of your Kaggle notebooks by specifying page number and page size.

Instructions

List your Kaggle notebooks (kernels)

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number (default: 1)
`pageSize`	No	Page size (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It indicates a read-like operation ('List') and scoping ('your'), but does not disclose whether the operation is read-only, if authentication is required, or what the response contains (e.g., metadata only). Critical behavioral traits are missing.

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 a single, concise sentence with no filler. It conveys the core purpose efficiently. However, it could include more details without becoming verbose, so not a perfect 5.

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

Completeness2/5

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

For a list tool with no output schema, the description should at least hint at the return format (e.g., 'returns a list of notebook objects with metadata'). The current description is too sparse, leaving the agent uncertain about what it will receive. Pagination semantics are covered in the schema, but overall completeness is lacking.

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 100% with clear descriptions and defaults for both parameters (page, pageSize). The description adds no additional meaning beyond what the schema already provides, so a 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 the action ('List') and the specific resource ('your Kaggle notebooks (kernels)'). It distinguishes from sibling tools like kaggle_search_datasets (public datasets) and kaggle_get_notebook_status (single notebook status) by specifying the scoping to the user's own notebooks.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention that it only lists the authenticated user's notebooks, nor does it suggest kaggle_search_datasets for finding public notebooks. Implied usage is minimal.

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

Deploy Server