Create a new Logseq page with optional initial content. Specify a page name to add it to your graph instantly.
Create a new page in Logseq
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The name of the page | |
| content | No | Optional initial content for the page |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It only restates the create action and gives no detail about side effects, duplicate-page behavior, whether content replaces or appends, or whether the operation has any irreversible consequences.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundant wording. Every word contributes to understanding the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with only 2 parameters and no output schema, so the minimal description is partially adequate. However, the lack of annotations and absence of behavioral context around duplicates or effects leaves minor but real gaps for an agent deciding whether and how to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter meaning, but the schema already documents 'name' as the page name and 'content' as optional initial content, which is sufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Create'), the resource ('page'), and the context ('Logseq'). It also distinguishes this tool from siblings like create_block (block creation) and get/update/search operations, so an agent can easily identify what this tool is for.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives such as create_block or update_block. It does not state exclusions, prerequisites, or scenarios where another sibling should be preferred, leaving the agent to infer usage from the name and description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.