Skip to main content
Glama

twenty

by io.usefulapi

List notes

twenty_list_notes
Read-only

List/filter notes. Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoHow deep to hydrate related records: 0, 1, or 2.
limitNoResults per page (1-60, default 20 — Twenty caps at 60).
filterNoRaw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike, startsWith.
order_byNoRaw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`.
ending_beforeNoPagination cursor — return records before this cursor (from a previous page's pageInfo).
starting_afterNoPagination cursor — return records after this cursor (from a previous page's pageInfo).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation by mentioning support for cursor pagination, raw filter/order_by, and relation depth. This informs the agent about advanced query capabilities. It does not describe auth requirements or rate limits, but the annotation already establishes the safe read-only nature.

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?

The description is three concise sentences, front-loaded with the purpose, followed by feature highlights and the REST endpoint. Every sentence earns its place with no redundant or unnecessary wording.

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?

Given that there is no output schema, the description should hint at return behavior. 'List/filter notes' implies a list result, and pagination cursors referencing pageInfo suggest the response structure. The description covers the tool's main capabilities well, though it could be slightly more explicit about the response format.

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 baseline is 3. The description mentions cursor pagination, raw filter/order_by, and relation depth, which map to parameters like starting_after/ending_before, filter/order_by, and depth. However, this adds no new syntax or meaning beyond what the schema already provides; it only summarizes the existing parameter descriptions.

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?

The description clearly states the tool's purpose as 'List/filter notes', which is a specific verb+resource. It distinguishes from siblings like twenty_get_note (single note retrieval) and twenty_create_note (creation) by explicitly mentioning listing and filtering. The added details about cursor pagination and raw filter/order_by further specify its function.

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 implies usage for listing/filtering notes but does not explicitly contrast with alternatives such as twenty_get_note for single-note retrieval. It provides no explicit 'when to use' or 'when not to use' guidance, though the resource name and behavior make the intended use reasonably clear.

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

All twenty toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool follows a clear action-entity pattern, so there is no overlap; even the metadata listing is distinct from record operations. No two tools could be confused.

Naming Consistency5/5

All tools use the twenty_<verb>_<entity> convention with verbs create/get/list/update, in lowercase snake_case. Naming is perfectly consistent across the set.

Tool Count4/5

20 tools is slightly above the typical well-scoped range but justified by five core entities each needing create/get/list/update. However, the count feels a bit heavy, especially without delete tools.

Completeness3/5

The server covers create, read, and list for all entities, and update for most, but lacks delete operations entirely and does not support updating notes. These are notable gaps in full lifecycle management.

Resources