Skip to main content
Glama

notes_list

Retrieve a paginated list of notes filtered by entity (deal, person, organization, lead), user, pinned flags, or sorted by date. Supports pagination up to 500 items.

Instructions

List notes with pagination and filtering options.

Returns a paginated list of notes. Use filters to narrow results by associated entity.

Workflow tips:

  • Filter by entity to get notes for specific deals, persons, organizations, or leads

  • Filter by user_id to get notes by specific user

  • Use pinned flags to filter pinned notes

  • Sort by add_time, update_time, or content

  • Use start/limit for pagination (default limit: 100, max: 500)

Common use cases:

  • List all notes for a deal: { "deal_id": 123 }

  • List all notes for a person: { "person_id": 456 }

  • List pinned notes: { "deal_id": 123, "pinned_to_deal_flag": true }

  • List notes by user: { "user_id": 789 }

  • Recent notes first: { "sort": "add_time", "sort_by": "desc" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deal_idNoFilter by deal ID
person_idNoFilter by person ID
org_idNoFilter by organization ID
lead_idNoFilter by lead ID
user_idNoFilter by user (creator) ID
sortNoField to sort by (e.g., add_time, update_time, content)
sort_byNoSort direction
pinned_to_deal_flagNoFilter notes pinned to deals
pinned_to_person_flagNoFilter notes pinned to persons
pinned_to_organization_flagNoFilter notes pinned to organizations
pinned_to_lead_flagNoFilter notes pinned to leads
startNoPagination start
limitNoNumber of items to return
Behavior4/5

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

With no annotations, the description effectively discloses behavior: returns a paginated list, supports pagination (start, limit, default 100, max 500), sorting, filtering by entity/user/pinned flags. Does not mention auth or rate limits, but these are likely system-level.

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?

Concise and well-structured with a clear header, summary, and bullet-pointed tips and examples. Every sentence adds value, front-loaded with the main purpose.

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?

Given 13 optional parameters and no output schema, the description covers pagination, filtering, sorting, and common use cases comprehensively. It is sufficient for an agent to correctly invoke the tool.

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%, baseline 3. Description enriches understanding by providing common use cases and examples showing parameter combinations (e.g., deal_id with pinned_to_deal_flag), default limit, and max limit.

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 'List notes with pagination and filtering options,' specifying the verb 'List' and resource 'notes'. It distinguishes from sibling tools like notes_create, notes_get, etc.

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?

Provides explicit workflow tips and common use cases with JSON examples. It explains when to use filters and pagination, but does not explicitly mention alternative tools for specific scenarios (e.g., notes_get for a single note).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server