Skip to main content
Glama

Create File

create_file

Create a board, doc or folder in Whimsical. Boards start empty: add diagrams, sticky notes, tables and wireframes with add_board_content, or individual shapes, text and connectors with edit (see how_to('board')). Files start empty: fill a doc with add_doc_content. Pass add_page_to_id to add the new file as a page next to an existing one: added to it if it is a multipage, to its multipage if it is a page of one, otherwise the file is first turned into a multipage holding it as the first page — the same as Add page in the app. Use it when the user asks for a new page, tab or sheet of an existing file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "title": "<title>"
    },
    "name": "create_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhat to create
titleYesName of the new file or folder
parent_idNoFolder, team, multipage or doc id (base58) to create in. A doc id nests the new file inside that doc's body. Find ids with file_tree or search. Defaults to the Private section. Can't be combined with add_page_to_id.
add_page_to_idNoId of a file or multipage to add the new file next to, as a new page (see description).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-read-only, non-destructive, non-idempotent, open-world), so the description correctly focuses on behavior: boards and docs start empty, and add_page_to_id can silently convert an existing file into a multipage. That multipage-conversion side effect is important context an agent could not infer from the schema.

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?

Front-loaded with the verb and resource, and every sentence carries information about downstream tools or parameter effects. The add_page_to_id explanation is a dense run-on with em-dashes that could be tightened, but nothing is truly redundant.

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

Completeness5/5

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

For a multi-mode creation tool with no output schema and complete schema coverage, the description covers what is created, the empty-state of new files, how to fill them, and the non-obvious page-nesting behavior. An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3, but the description adds real meaning beyond the schema for add_page_to_id, whose own schema text defers to the description ('see description'), and clarifies the parent_id/add_page_to_id interaction. The 'type' enum values are only enumerated in the schema, which caps this at 4.

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 first sentence states a specific verb and resource: 'Create a board, doc or folder in Whimsical.' It then distinguishes the tool from siblings by naming add_board_content, add_doc_content and edit as the paths for populating content afterwards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names concrete alternatives (add_board_content, add_doc_content, edit) and gives an explicit trigger for the add_page_to_id mode: 'Use it when the user asks for a new page, tab or sheet of an existing file.' There is no explicit statement of when not to create a file, but the routing guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.