Skip to main content
Glama
Sign In
GetNote MCP Server

GetNote MCP Server

by iswalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_notes

Find notes by source, referenced resource, or knowledge base and return locator details for follow-up retrieval, with filters and pagination for reliable discovery.

Instructions

按来源、引用资源或知识库查找笔记。列表只返回定位信息；少量个人笔记正文按需用get_notes，知识库共享笔记保持get_note原权限路径。新查询核对meta.capabilities、applied_filters并按pagination.next_cursor翻页；partial/warnings未解决时末页也不代表来源完整。书库无匹配可按note_type=ref列定位信息，在真实reference中核对书籍作者/书名/book_id；保留时间、平台和知识库范围，平台未知不自加dedao，一次发现最多5页，未遍历完说明未查完。book_info.author与reference.author冲突须分别标注，候选不直接认定作者身份。total_count=null表示未知。

Input Schema

NameRequiredDescriptionDefault
pageNo知识库内可用页码；与 cursor 互斥
cursorNo首次省略。来源/类型/时间等新筛选使用pagination.next_cursor，保持原条件和page_size，直到has_more=false；仅旧默认列表沿旧响应cursor继续。不转换、不复用其他来源游标。
sourceNo笔记真实来源精确筛选：vendor_moan=AI录音台/墨案MOAN录音台，getseed=GetSeed录音卡（长录音与闪念），dedao=得到。查设备全部笔记只加来源，不额外限定audio/meeting；未限定设备时不加设备来源。
topic_idNo知识库 ID，限定授权范围
edited_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
note_typeNo真实类型精确筛选：ref=引用划线，audio=即时/普通录音，local_audio=上传音频文件，class_audio=自己录制的课堂笔记，meeting=会议，internal_record=内录，recorder_audio/recorder_flash_audio=录音卡长录音/闪念。录音不默认限定dedao或课程。
page_sizeNo每页 1–100 条，默认 20
created_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
edited_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
created_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
record_updated_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
record_updated_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
reference_course_idNo真实课程容器ID字符串，来自list_reference_resources；不使用课节resource_id替代
reference_article_urlNo文章 URL 精确筛选，保留 query 和 fragment
reference_course_typeNo课程容器类型，当前66；与reference_course_id配对，source=dedao，个人笔记，不与topic_id组合
reference_resource_idNo引用资源 ID，必须字符串；同时传 source 和 reference_resource_type
reference_resource_typeNo引用资源类型，如 ebook、course_article、audio_book

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv1.10.1
    • addedInput schema / properties / created_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / created_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "首次省略。来源/类型/时间等新筛选使用pagination.next_cursor，保持原条件和page_size，直到has_more=false；仅旧默认列表沿旧响应cursor继续。不转换、不复用其他来源游标。",
+  "type": "string"
+}
    • addedInput schema / properties / edited_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / edited_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / note_type
      Added value: +{
+  "description": "真实类型精确筛选：ref=引用划线，audio=即时/普通录音，local_audio=上传音频文件，class_audio=自己录制的课堂笔记，meeting=会议，internal_record=内录，recorder_audio/recorder_flash_audio=录音卡长录音/闪念。录音不默认限定dedao或课程。",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "知识库内可用页码；与 cursor 互斥",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "每页 1–100 条，默认 20",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / record_updated_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / record_updated_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / reference_article_url
      Added value: +{
+  "description": "文章 URL 精确筛选，保留 query 和 fragment",
+  "type": "string"
+}
    • addedInput schema / properties / reference_course_id
      Added value: +{
+  "description": "真实课程容器ID字符串，来自list_reference_resources；不使用课节resource_id替代",
+  "type": "string"
+}
    • addedInput schema / properties / reference_course_type
      Added value: +{
+  "description": "课程容器类型，当前66；与reference_course_id配对，source=dedao，个人笔记，不与topic_id组合",
+  "type": "string"
+}
    • addedInput schema / properties / reference_resource_id
      Added value: +{
+  "description": "引用资源 ID，必须字符串；同时传 source 和 reference_resource_type",
+  "type": "string"
+}
    • addedInput schema / properties / reference_resource_type
      Added value: +{
+  "description": "引用资源类型，如 ebook、course_article、audio_book",
+  "type": "string"
+}
    • removedInput schema / properties / since_id
      Removed value: -{
-  "default": 0,
-  "description": "游标，返回 ID 小于此值的笔记。首次传 0",
-  "type": [
-    "number",
-    "string"
-  ]
-}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "笔记真实来源精确筛选：vendor_moan=AI录音台/墨案MOAN录音台，getseed=GetSeed录音卡（长录音与闪念），dedao=得到。查设备全部笔记只加来源，不额外限定audio/meeting；未限定设备时不加设备来源。",
+  "type": "string"
+}
    • addedInput schema / properties / topic_id
      Added value: +{
+  "description": "知识库 ID，限定授权范围",
+  "type": "string"
+}
  2. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does: it says the list returns only locating info, that partial/warnings mean even the last page may be incomplete, that total_count=null means unknown, and that meta.capabilities/applied_filters/pagination.next_cursor must be checked. It also discloses a hard 5-page discovery limit and conflict-annotation rules for book_info.author vs reference.author.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is a dense run-on chain of semicolon-separated rules (pagination, partials, discovery cap, author conflicts) with no grouping, which makes it easy to miss individual constraints.

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?

For a 17-parameter tool with no annotations and no output schema, the description supplies the missing return-shape semantics (meta.capabilities, applied_filters, pagination.next_cursor, partial/warnings, total_count=null). Only edge behavior around permission failures and empty-result handling remains thin.

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%, so the baseline is 3; the prose adds cross-parameter constraints and intent beyond the schema, e.g. keeping time/platform/knowledge-base scope together, not adding a default dedao source, and how to use note_type=ref plus real reference fields to resolve book author/title/book_id.

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?

States a specific verb and resource (查找笔记) plus the three filtering axes (来源、引用资源、知识库), and immediately distinguishes the tool from get_notes (body retrieval) and get_note (knowledge-base shared notes path). An agent can pick this over its siblings without opening the schema.

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?

Explicitly routes body retrieval to get_notes and notes the original permission path via get_note for knowledge-base shared notes, plus concrete rules for unknown platforms (don't auto-add dedao) and a 5-page discovery cap. It gives context but no explicit statement of when NOT to use this tool overall.

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