Skip to main content
Glama

list_memos

Retrieves flomo notes: recent updates, full chronological pages, or filtered by tag with sub-tag inclusion.

Instructions

列出笔记。mode=recent 最近更新(最新在前,最多200条);mode=all 全量按时间升序游标翻页(每页最多100条);传 tag 按标签过滤(前缀匹配含子标签,如 阅读 也含 阅读/读书,全量扫描后按更新时间降序翻页,忽略 mode)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_memos"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo按标签过滤(前缀匹配含子标签,如 阅读 也含 阅读/读书)。传此参数时忽略 mode,全量扫描后本地过滤,按更新时间降序游标翻页
modeNorecent=最近更新(最新在前,最多200条);all=全量按时间升序翻页(每页≤100)。传 tag 时忽略recent
limitNo返回条数(mode=all 时每页最多 100 条,超出按 100 执行)
cursorNo翻页游标(上次返回的 next_cursor;mode=all 或传 tag 时使用,后者翻页须保持 tag 不变)

Output Schema

NameRequiredDescriptionDefault
tagNo本次过滤的标签(已去除 # 前缀);存在即本次为 tag 过滤结果
modeNo本次使用的模式;传 tag 过滤时不返回
countYes本次返回条数(非全量总数)
memosYes
matchedNotag 过滤:匹配总数
scannedNotag 过滤:本次实际扫描笔记数
completeNotag 过滤:false=触达 40 页扫描上限,结果可能不全
next_cursorNo存在即还有下一页,原样传入下次调用

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses result caps (200 for recent, 100 per page for all), ordering (newest-first vs ascending by time), and that tag filtering triggers a full scan with descending-by-update-time pagination. It still leaves the read-only nature and any permission requirements unstated, but those are minor in context.

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?

A single dense sentence that front-loads the core action and then layers mode behavior, tag behavior, and pagination in order. Every clause carries information, though some of it duplicates the schema text.

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?

An output schema exists, so return values need not be explained, and the description covers ordering, page limits, cursor usage, and the tag-overrides-mode rule. That is sufficient for an agent to call it correctly; only sibling routing remains uncovered.

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 every parameter, including the tag prefix-match behavior and the cursor requirement. The description mostly restates those facts rather than adding new semantics, so the baseline of 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?

States a specific verb and resource ("列出笔记", list memos) and details the two listing modes. It is clear what the tool does, but it never distinguishes itself from siblings like search_memos or list_tags, leaving that to the caller.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful mode-selection guidance (recent vs all) and explains that the tag parameter overrides mode, which implicitly tells the agent which mode to pick. However, there is no explicit when-to-use vs. when-not-to-use, and no mention of when to prefer search_memos for content search.

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