quillink-mcp

list_notes

Retrieve and filter Quillink notes by folder, status, tags, pinned state, and limit; locked note bodies are withheld as null.

Instructions

List the caller's notes. folder_id="" lists notes with no folder; omit it to list across all folders. status is "active" or "trashed". tags filters to notes with any of them, or every one of them with tag_match="all". Locked notes are included but their body is withheld (null).

Input Schema

Name	Required	Default
`tags`	No
`limit`	No
`pinned`	No
`status`	No	active
`folder_id`	No
`tag_match`	No	any
`start_after`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedInput schema / properties / tag_match

Added value: +{
+  "default": "any",
+  "title": "Tag Match",
+  "type": "string"
+}

First observedv0.1.0Aug 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose several non-obvious behaviors: the empty-string vs omitted folder_id distinction, the active/trashed status values, tag OR-vs-AND semantics, and that locked notes appear with a null body. It does not mention pagination (limit/start_after) or result ordering, which for a listing tool is a notable omission.

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?

Four tight sentences, no filler, and the core operation is front-loaded. Each sentence carries distinct information about filter behavior, so nothing needs to be cut.

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-value explanation is not required, and the description covers the semantically tricky filters plus the locked-note edge case. It is still incomplete for a 7-parameter list tool: pagination and ordering parameters receive no mention, and no sibling is referenced for routing.

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 0%, so the description must compensate. It clarifies the tricky cases for folder_id, status, tags and tag_match, but leaves limit, pinned and start_after completely unexplained, meaning three of seven parameters have no semantic guidance anywhere.

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?

"List the caller's notes" gives a specific verb and resource, and "caller's" scopes it to the authenticated user's own notes rather than shared ones. It does not name the adjacent sibling list_shared_notes or search_notes to explain the boundary, so differentiation is left to inference.

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?

The description explains filter semantics (empty folder_id vs omitted, status values, tag_match modes) which tells an agent how to use it correctly, but gives no explicit when-to-use versus search_notes / list_shared_notes / list_folders. Usage is implied rather than routed.

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