Skip to main content
Glama
Sign In
Inkdrop MCP Server

Inkdrop MCP Server

Official
by inkdropapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list-notes

List and filter notes by notebook, tags, keyword, sort order, and limit; use read-note to fetch full content when previews are truncated.

Instructions

List all notes with specified conditions. The result does not include entire note bodies as they are truncated in 200 characters. You have to retrieve the full note content by calling read-note.

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-notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort the documents by the specified fieldupdatedAt
limitNoLimit the number of results returned
bookIdNoID of the notebook. It always starts with 'book:'. You can retrieve a list of notebooks with `list-notebooks`. The pseudo-notebooks 'trash' and 'template' are not supported here; use `list-templates` for templates
tagIdsNoAn array of tag IDs to filter. It always starts with 'tag:'. You can retrieve a list of available tags from `list-tags`.
keywordNoKeyword to filter notes
descendingNoReverse the order of the output documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / bookId / description
      Previous value: -"ID of the notebook. It always starts with 'book:'. You can retrieve a list of notebooks with `list-notebooks`"New value: +"ID of the notebook. It always starts with 'book:'. You can retrieve a list of notebooks with `list-notebooks`. The pseudo-notebooks 'trash' and 'template' are not supported here; use `list-templates` for templates"
  2. First observedv1.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a genuinely important behavioral trait not in the schema: results truncate note bodies at 200 characters and full content requires `read-note`. It omits other behaviors such as default result ordering, what happens at the limit boundary, or pagination for large result sets.

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?

Three short sentences, front-loaded with the purpose followed immediately by the most important caveat. No filler; the only minor inefficiency is the slightly awkward phrasing of the truncation sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to explain the shape of the result (truncated bodies) and the exact remediation path (`read-note`). Combined with a fully documented six-parameter schema, an agent has everything needed to call this correctly and interpret the response.

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%, and the schema itself documents sorting fields, the bookId prefix convention, tag ID format, and defaults. The description adds no parameter-level meaning beyond that, which is acceptable given full schema coverage but not additive.

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 all notes') with a scoping qualifier ('specified conditions'). It is clear what the tool does, but it never contrasts itself with the sibling `search-notes`, which sounds like it does something very similar, so the agent must guess which to pick.

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 gives one concrete routing instruction: use `read-note` to get untruncated bodies. That is useful usage guidance for the follow-up step. However, there is no guidance on when to use this versus `search-notes` or `list-templates`, which is the primary selection ambiguity for this tool.

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