Kaggle MCP Server

Overview Schema Source Related Servers Discussions Admin

model_create

Create a new Kaggle model with specified owner, slug, and title. Set privacy and add optional subtitles or descriptions.

Instructions

Create a new Kaggle model.

    Args:
        owner: Owner username.
        slug: Model slug (URL-friendly identifier).
        title: Model title.
        subtitle: Optional subtitle.
        description: Optional description.
        is_private: Whether the model is private (default True).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes
`owner`	Yes
`title`	Yes
`subtitle`	No
`is_private`	No
`description`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, and description does not disclose behavioral traits like auth requirements, idempotency, error handling, or side effects. The description only states the action without further context.

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?

Description is concise with a clear purpose followed by a bullet-like list of parameters. No redundant sentences, well-structured.

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?

Covers all parameters but lacks information about return values or behavior (e.g., does it return the created model? what happens on conflict?). With an output schema available, description could still benefit from brief return info.

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 0%, but description adds one-line explanations for each parameter (e.g., 'Owner username.'). Adds some meaning beyond the schema's titles and defaults, but lacks detail on constraints or formats.

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?

Clearly states 'Create a new Kaggle model' with specific verb and resource. Lists required parameters. Does not explicitly differentiate from siblings like model_update or model_instance_create, but purpose is clear.

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 (e.g., model_instance_create). No prerequisites or exclusions mentioned. Usage is only implied by the action.

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

Deploy Server