Skip to main content
Glama
ergut

MCP server for LogSeq

by ergut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_pages

List all pages in a LogSeq graph with last-updated times. Sort by update time or filter by date to find recently modified pages.

Instructions

Lists all pages in a LogSeq graph, each with its last-updated time (UTC). To find recently modified pages, use sort='updated' (most recent first) and/or updated_since.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by page name (default) or by last update, most recent first (pages without an update time go last).name
limitNoReturn at most this many pages (applied after filtering and sorting). Omit for all.
updated_sinceNoOnly pages updated at or after this time: epoch milliseconds, or an ISO-8601 date/datetime (naive values are UTC). Pages without an update time are excluded.
include_journalsNoWhether to include journal/daily notes in the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • changedInput schema / properties / limit / description
      Previous value: -"Return at most this many pages (alphabetical). Omit for all."New value: +"Return at most this many pages (applied after filtering and sorting). Omit for all."
    • addedInput schema / properties / sort
      Added value: +{
+  "default": "name",
+  "description": "Sort by page name (default) or by last update, most recent first (pages without an update time go last).",
+  "enum": [
+    "name",
+    "updated"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / updated_since
      Added value: +{
+  "description": "Only pages updated at or after this time: epoch milliseconds, or an ISO-8601 date/datetime (naive values are UTC). Pages without an update time are excluded.",
+  "type": [
+    "integer",
+    "string"
+  ]
+}
  2. Changed1 schema field changedv1.9.2
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Return at most this many pages (alphabetical). Omit for all.",
+  "minimum": 1,
+  "type": "integer"
+}
  3. 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 supplied, so the description carries the whole burden. It discloses that timestamps are UTC and that results include an update time, but says nothing about read-only safety, pagination beyond the schema's limit, or permissions. For a low-risk list operation this is acceptable but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the core purpose front-loaded and the usage hint following immediately. Every clause earns its place.

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?

With no annotations and no output schema, the description still covers what the tool returns at a high level and how to target recent pages, which is enough to call it correctly. Minor gaps remain around safety/pagination behavior.

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 sort, limit, updated_since and include_journals in detail. The description's mention of sort='updated' and updated_since restates rather than extends that information, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Lists all pages in a LogSeq graph') and adds what each item carries ('last-updated time (UTC)'). It is distinguishable from siblings like find_pages_by_property or get_pages_from_namespace, though it never names an alternative explicitly.

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?

It gives explicit guidance for a common sub-task: 'To find recently modified pages, use sort="updated" ... and/or updated_since.' That is clear contextual usage, but it does not state when to prefer this tool over siblings such as query or search.

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