Skip to main content
Glama
ergut

MCP server for LogSeq

by ergut

create_page

Create a new page in Logseq, parsing Markdown into block hierarchy. Fails if page exists, making retries safe.

Instructions

Create a new page in Logseq with properly structured blocks.

Fails if a page with the same title already exists (use update_page to modify existing pages). This makes retries safe: re-sending a create_page that timed out will not create numbered duplicates like "Page(1)".

Markdown content is automatically parsed into Logseq's block hierarchy:

  • Headings (# ## ###) create nested sections

  • Lists (- or 1.) become proper block trees

  • Code blocks are preserved as single blocks

  • YAML frontmatter (---) becomes page properties

Example content:

---
tags: [project, active]
priority: high
---

# Project Title
Introduction paragraph.

## Tasks
- Task 1
  - Subtask A
- Task 2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the new page
contentNoMarkdown content to parse into blocks (optional)
propertiesNoPage properties (merged with frontmatter if both provided)
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses failure on duplicate titles, retry safety, markdown parsing into block hierarchy, and property merging. Could mention return value or side effects, but covers key behaviors.

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?

Well-structured with sections, example, and clear explanations. Slightly long but each part serves a purpose. No wasted sentences.

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?

Covers input semantics, behavior, and constraints. Missing return value description, but given the tool's simplicity and no output schema, it is sufficiently complete for page creation.

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% (baseline 3). Description adds meaning by explaining how 'content' is parsed (markdown into blocks) and that 'properties' merge with frontmatter. Adds value beyond the schema.

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 action ('Create a new page') and the resource ('in Logseq with properly structured blocks'). It distinguishes from sibling tools like update_page by noting the fail condition for duplicate titles.

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

Usage Guidelines5/5

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

Explicitly states when to use (creating new pages) and when not to (if page exists, use update_page). Also explains retry safety, providing clear guidance for the agent.

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/ergut/mcp-logseq'

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