Create a new Kaggle dataset by uploading a local folder. Specify directory path, set visibility, and add metadata to publish datasets directly from your environment.
Create a new dataset from a folder
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| public | No | ||
| dir_path | Yes | ||
| subtitle | No | ||
| description | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears the full burden of behavioral disclosure. It indicates a create operation but does not explain side effects, whether existing datasets are overwritten, permission requirements, upload behavior, or what happens on failure. This is minimal for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler; the verb and resource appear immediately. It is appropriately concise, though it achieves brevity at the cost of useful detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, no annotations, and a large sibling toolset, this description is incomplete. It does not convey required path format, optional field behavior, response semantics, or how this differs from similar dataset tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and there are 5 parameters, but the description only hints at the meaning of dir_path through 'from a folder'. It provides no semantics for name, public, subtitle, or description, leaving the agent without meaningful parameter guidance beyond the required field name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Create') on a clear resource ('a new dataset') and identifies the source ('from a folder'). However, it does not differentiate from sibling tools like init_dataset or update_dataset, which could also be associated with dataset creation or modification.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as init_dataset or update_dataset. The phrase 'from a folder' implies a use case, but no explicit context, prerequisites, or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.