Skip to main content
Glama
Sign In
Logseq MCP Server

Logseq MCP Server

by dailydaniel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

logseq_insert_block

Insert new blocks into Logseq to create page-level or nested blocks, manage properties, and set custom UUIDs. Specify positioning relative to parent blocks for precise organization and reference.

Instructions

Insert a new block into Logseq. Can create: - Page-level blocks (use is_page_block=true with page name as parent_block) - Nested blocks under existing blocks - Blocks with custom UUIDs for precise reference Supports before/after positioning and property management.

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": {
      "content": "<content>"
    },
    "name": "logseq_insert_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNoInsert before parent
contentYesContent of the new block
custom_uuidNoCustom UUID for block
is_page_blockNoPage-level block flag
parent_blockNoUUID or content of parent block

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/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 key behavioral traits like support for 'before/after positioning and property management,' which are not obvious from the schema alone. However, it lacks details on permissions needed, error conditions, or what happens on failure, leaving gaps for a mutation tool.

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 appropriately sized and front-loaded, starting with the core action and immediately listing capabilities in a bullet-like structure. Every sentence adds value, though the formatting with colons and dashes could be slightly cleaner for optimal readability.

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?

Given the complexity of a block insertion tool with 5 parameters, no annotations, and no output schema, the description is moderately complete. It covers key use cases and parameters but lacks information on return values, error handling, or integration with sibling tools, leaving some contextual gaps for an agent to operate effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning 'before/after positioning' (hinting at the 'before' parameter) and 'custom UUIDs' (referencing 'custom_uuid'), but does not provide additional semantics beyond what the schema specifies, meeting the baseline for high coverage.

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 ('Insert a new block') and resource ('into Logseq'), distinguishing it from siblings like logseq_create_page (creates pages) and logseq_edit_block (modifies existing blocks). It provides concrete examples of what can be created, making the purpose unambiguous and differentiated.

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?

The description provides clear context on when to use this tool by listing the types of blocks it can create (page-level, nested, with custom UUIDs). However, it does not explicitly state when NOT to use it or name specific alternatives among the sibling tools, such as using logseq_create_page for creating new pages instead of page-level blocks.

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

Deploy Server

Other Tools

Related Tools