Skip to main content
Glama
dweigend

Joplin MCP Server

by dweigend

create_note

Create a new note in Joplin with title, markdown content, optional parent folder, and todo status.

Instructions

Create a new note in Joplin.

Args:
    args: Note creation parameters
        title: Note title
        body: Note content in Markdown (optional)
        parent_id: ID of parent folder (optional)
        is_todo: Whether this is a todo item (optional)

Returns:
    Dictionary containing the created note data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Implementation Reference

  • MCP tool handler function for 'create_note', registered via @mcp.tool() decorator. Calls JoplinAPI.create_note to perform the creation.
    @mcp.tool()
    async def create_note(args: CreateNoteInput) -> Dict[str, Any]:
        """Create a new note in Joplin.
        
        Args:
            args: Note creation parameters
                title: Note title
                body: Note content in Markdown (optional)
                parent_id: ID of parent folder (optional)
                is_todo: Whether this is a todo item (optional)
        
        Returns:
            Dictionary containing the created note data
        """
        if not api:
            return {"error": "Joplin API client not initialized"}
        
        try:
            note = api.create_note(
                title=args.title,
                body=args.body,
                parent_id=args.parent_id,
                is_todo=args.is_todo
            )
            return {
                "status": "success",
                "note": {
                    "id": note.id,
                    "title": note.title,
                    "body": note.body,
                    "created_time": note.created_time.isoformat() if note.created_time else None,
                    "updated_time": note.updated_time.isoformat() if note.updated_time else None,
                    "is_todo": note.is_todo
                }
            }
        except Exception as e:
            logger.error(f"Error creating note: {e}")
            return {"error": str(e)}
  • Pydantic input schema/model for the create_note tool parameters.
    class CreateNoteInput(BaseModel):
        """Input parameters for creating a note."""
        title: str
        body: Optional[str] = None
        parent_id: Optional[str] = None
        is_todo: Optional[bool] = False
  • JoplinAPI.create_note method implementing the HTTP POST request to Joplin's /notes endpoint to create the note.
    def create_note(
        self,
        title: str,
        body: str | None = None,
        parent_id: str | None = None,
        is_todo: bool = False
    ) -> JoplinNote:
        """Create a new note.
    
        Args:
            title: Note title
            body: Note content in Markdown
            parent_id: ID of parent folder
            is_todo: Whether this is a todo item
    
        Returns:
            Created JoplinNote object
        """
        data = {
            "title": title,
            "is_todo": is_todo
        }
    
        if body is not None:
            data["body"] = body
    
        if parent_id is not None:
            data["parent_id"] = parent_id
    
        response = self._make_request("POST", "notes", json=data)
        return JoplinNote.from_api_response(response)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a note but doesn't mention authentication requirements, rate limits, error conditions, or what happens if parent_id is invalid. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured with clear sections (Args, Returns) and uses bullet points for parameters. It's appropriately sized, though the 'Args: args:' phrasing is slightly redundant. Every sentence adds value, with no wasted words.

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

Completeness3/5

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

For a creation tool with no annotations and no output schema, the description adequately covers the basic purpose and parameters. However, it lacks details about return values (only mentions 'dictionary containing the created note data' without specifics), error handling, or behavioral constraints, leaving room for improvement given the mutation nature of the tool.

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?

The description provides comprehensive parameter details beyond the schema, which has 0% description coverage. It explains each parameter's purpose (title, body, parent_id, is_todo), marks optionality, and clarifies that body is in Markdown format, fully compensating for the schema's lack of descriptions.

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 clearly states the specific action ('Create a new note') and resource ('in Joplin'), distinguishing it from sibling tools like delete_note, get_note, update_note, search_notes, and import_markdown. The verb 'create' is precise and unambiguous.

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 provided on when to use this tool versus alternatives like update_note or import_markdown. The description lacks context about prerequisites (e.g., needing a valid parent_id) or scenarios where this tool is appropriate, offering only basic functional information.

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/dweigend/joplin-mcp-server'

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