Skip to main content
Glama

notes_create

Create and attach notes to deals, people, organizations, or leads with support for HTML content, pinning, and backdating.

Instructions

Create a new note and attach it to a deal, person, organization, or lead.

Creates a note with the specified content and associates it with one or more entities.

Workflow tips:

  • content is required and supports HTML formatting

  • At least one entity should be specified (implicitly via schemas)

  • Set pinned flags to pin note to specific entities

  • user_id sets the note creator (defaults to authenticated user)

  • add_time can be specified for backdating notes

  • Content supports rich text and can include formatting

Common use cases:

  • Simple note: { "content": "Follow up next week", "deal_id": 123 }

  • Pinned note: { "content": "Important info", "person_id": 456, "pinned_to_person_flag": true }

  • Multi-entity note: { "content": "Meeting notes", "deal_id": 123, "person_id": 456 }

  • Rich text note: { "content": "Action items:Send proposal", "deal_id": 789 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesNote content (required, supports HTML, max 65000 chars)
deal_idNoID of the deal to attach to
person_idNoID of the person to attach to
org_idNoID of the organization to attach to
lead_idNoID of the lead to attach to
user_idNoID of the user who created the note
add_timeNoCreation time in YYYY-MM-DD HH:MM:SS format
pinned_to_deal_flagNoPin note to deal
pinned_to_person_flagNoPin note to person
pinned_to_organization_flagNoPin note to organization
pinned_to_lead_flagNoPin note to lead
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors (e.g., content supports HTML, entity attachment, pinning, user_id, backdating). However, it omits the return value or side effects, which is a gap given the absence of an output schema.

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 concise yet comprehensive, structured with a one-line summary, workflow tips, and common use cases. Every sentence adds value without unnecessary repetition, making it easy to scan.

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

Completeness3/5

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

Given the tool's complexity (11 parameters, no output schema, no annotations), the description partially compensates by explaining parameters and providing examples. However, it lacks information about the response format or what happens on success, leaving some questions unanswered.

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?

The input schema already has 100% coverage with descriptions for all 11 parameters. The description adds value beyond the schema by explaining usage patterns (e.g., 'At least one entity should be specified', 'Set pinned flags') and providing concrete examples, making parameter semantics clearer.

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 function: 'Create a new note and attach it to a deal, person, organization, or lead.' It uses a specific verb (create) and resource (note), and distinguishes it from sibling tools like notes_update or notes_delete by focusing on creation.

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?

The description provides workflow tips and common use cases that illustrate when to use various parameter combinations, such as pinned notes or multi-entity notes. However, it does not explicitly state when not to use this tool versus alternatives like notes_update, leaving room for improvement.

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