Skip to main content
Glama

Logseq MCP Tools

by apw124

move_block

Move a block and its children to a new location in Logseq graphs. Choose to position it as a child or sibling of the target block using the 'as_child' parameter.

Instructions

Moves a block to a new location in the graph. This allows for reorganizing the structure of blocks in the graph by moving a block (and all its children) to a different location. IMPORTANT NOTES: 1. The block will maintain its children when moved 2. The hierarchical position depends on the 'as_child' parameter: - If as_child=True: The block becomes a child of the target block - If as_child=False: The block becomes a sibling after the target block Args: block_id (str): The ID of the block to move. target_block_id (str): The ID of the target block to move to. as_child (bool, optional): Whether to make the block a child of the target. Default is False (insert as sibling). Returns: dict: Result of the move operation.

Input Schema

NameRequiredDescriptionDefault
as_childNo
block_idYes
target_block_idYes

Input Schema (JSON Schema)

{ "properties": { "as_child": { "default": false, "title": "As Child", "type": "boolean" }, "block_id": { "title": "Block Id", "type": "string" }, "target_block_id": { "title": "Target Block Id", "type": "string" } }, "required": [ "block_id", "target_block_id" ], "title": "move_blockArguments", "type": "object" }

You must be authenticated.

Other Tools from Logseq MCP Tools

Related Tools

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

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