create_fileCreate a private document or folder in Files. Documents require a text, base64, or asset source. Asset sources copy without deleting the source. Folders have no source. Name conflicts never overwrite.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | ||
| name | Yes | ||
| source | No | Required when kind is file. Omit when kind is folder. | |
| parentId | No | ||
| projectId | Yes |
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / parentId / anyOfPrevious value: -[
- {
- "format": "uuid",
- "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
- "type": "string"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "format": "uuid",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / projectId / patternRemoved value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Input schema / properties / source / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "contentType": {
- "maxLength": 255,
- "minLength": 1,
- "type": "string"
- },
- "text": {
- "type": "string"
- },
- "type": {
- "const": "text",
- "type": "string"
- }
- },
- "required": [
- "type",
- "text"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "contentType": {
- "maxLength": 255,
- "minLength": 1,
- "type": "string"
- },
- "dataBase64": {
- "type": "string"
- },
- "type": {
- "const": "base64",
- "type": "string"
- }
- },
- "required": [
- "type",
- "dataBase64",
- "contentType"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "assetId": {
- "format": "uuid",
- "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
- "type": "string"
- },
- "type": {
- "const": "asset",
- "type": "string"
- }
- },
- "required": [
- "type",
- "assetId"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "contentType": {
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+ },
+ "text": {
+ "type": "string"
+ },
+ "type": {
+ "const": "text",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "text"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "contentType": {
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+ },
+ "dataBase64": {
+ "type": "string"
+ },
+ "type": {
+ "const": "base64",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "dataBase64",
+ "contentType"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "assetId": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "type": {
+ "const": "asset",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "assetId"
+ ],
+ "type": "object"
+ }
+]Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare the mutation safety profile (non-destructive, non-idempotent), and the description adds genuinely new behavioral facts: asset sources are copied without deleting the original, and name conflicts never overwrite. These are exactly the kind of side-effect disclosures an agent needs beyond the annotations.
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?
Four compact sentences, front-loaded with the core action, each adding a distinct behavioral fact. No filler, though the source-requirement sentence is somewhat dense.
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?
For a mutation tool with no output schema and low schema coverage, the description covers the trickiest parameter (source) and key side effects, but omits where the file is placed (parentId/projectId) and what is returned. Adequate but with clear gaps.
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 coverage is only 20%, so the description carries real weight. It correctly explains the source requirement logic (text/base64/asset for files, omitted for folders), but leaves projectId, parentId, and name constraints undocumented in both schema and description.
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?
States a specific verb and resource ('Create a private document or folder in Files') and clarifies the file-vs-folder distinction. It is clearly separable from siblings like get_file or upload_asset, though it doesn't explicitly contrast itself with those.
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?
The file/folder distinction implies when to use which kind, but there is no explicit guidance on when to choose this over upload_asset or create_artifact, nor any stated prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.