Skip to main content
Glama
biontdv

joplin-mcp

by biontdv

create_note

Create a Joplin note with a title, Markdown body, and optional notebook selection. Can also create as a to-do item.

Instructions

Create a new note.

Args:
    title: Note title.
    body: Note body in Markdown.
    notebook_id: Target notebook (folder) id. If omitted, Joplin uses the
        currently selected notebook in the app.
    is_todo: If true, create the note as a to-do item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
titleYes
is_todoNo
notebook_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the notebook_id default ('currently selected notebook in the app') and the is_todo behavior, but it does not mention side effects, return values, permissions, or error behavior. For a mutation tool, this is a significant gap.

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?

The description is front-loaded with the one-line purpose and then lists arguments in a clean, scannable format. Every sentence serves a purpose, with no extraneous wording.

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

Completeness4/5

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

For a simple create operation with an output schema, the description adequately explains parameter semantics and defaults. It lacks usage guidance and behavioral details, but these are separate dimensions. Overall, it is sufficiently complete for the tool's complexity.

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 description coverage is 0%, so the description must add meaning. It explains body as 'Markdown', notebook_id's default behavior, and is_todo's effect. However, title is described only as 'Note title,' which adds little beyond the schema's property name.

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 description opens with 'Create a new note,' a specific verb+resource statement that clearly distinguishes this tool from siblings like create_notebook and update_note. It unambiguously states the tool's function.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'Create' and the note-related context, but the description does not explicitly state when to use this tool versus alternatives like update_note or provide any exclusions. No alternative tools are referenced.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/biontdv/Joplin-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server