lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

notion_create_file_upload

DestructiveIdempotent

Create a file upload in Notion through the governed connector. Provide project and connector account details to route the upload securely and complete the operation.

Instructions

Notion connector operation create_file_upload (platform tool notion.create_file_upload).

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Claimed read or write effect; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema

Name	Required	Default
`effect`	No
`arguments`	No	{}
`project_id`	No
`project_ref`	No
`approval_ref`	No
`idempotency_key`	No
`connector_account_ref`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.1Sep 7, 2026

addedInput schema / properties / approval_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}

addedInput schema / properties / connector_account_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}

addedInput schema / properties / effect

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Effect"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}

addedInput schema / properties / project_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}

First observedv0.1.0Jun 25, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already communicate safety and mutability, so the description carries a lower burden. It does add useful governance context: effect is 'claimed' and verified by Spring, and write resumption requires an approval_ref. However, it never discloses what side effects occur, whether an upload session is created, or what the destructive aspect hinted by destructiveHint=true actually is.

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 compact and the parameter list is scannable. The first sentence is somewhat redundant with the tool name, but the rest is information-dense without excessive prose. It earns a high score for structure despite the redundant opening.

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?

The description omits the actual semantics of the Notion 'create_file_upload' operation and the expected payload inside the generic arguments JSON string. It also does not situate this tool within the broader file-upload flow suggested by sibling tools like notion_send_file_upload and notion_complete_file_upload. An agent would struggle to invoke it correctly even though the governance parameters are well documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the Args section fully compensates by giving a meaningful one-line explanation for all seven parameters. Terms like 'Authenticated Project UUID', 'Stable business-action identity', and 'Approved platform task UUID when resuming a write' add real semantic value beyond the bare property names and schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens by restating the tool name as 'Notion connector operation `create_file_upload`' without explaining what the operation actually does or what 'create file upload' means in Notion's upload lifecycle. The only other purpose-related sentence is about routing authority, not about behavior. This is closer to a tautology than a functional description.

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 given about when to use this tool versus sibling tools such as notion_send_file_upload, notion_complete_file_upload, or notion_get_file_upload. The phrase 'Routes only through the exact project/account governed connector authority' is a routing constraint, not a usage condition. An agent cannot determine the correct step in the Notion file-upload workflow from this description.

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

Deploy Server