Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createNote

Add a note to a Follow Up Boss contact by person ID, with optional subject and HTML body, to record call details, follow-ups, or context.

Instructions

Create a note on a person.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personId": "<personId>"
    },
    "name": "createNote"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNote content.
isHtmlNotrue = render HTML tags in body.
subjectNoNote title.
personIdYesPerson ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • changedInput schema / properties / body / description
      Previous value: -"Note body/content"New value: +"Note content."
    • removedInput schema / properties / createdAt
      Removed value: -{
      -  "description": "ISO timestamp",
      -  "type": "string"
      -}
    • addedInput schema / properties / isHtml
      Added value: +{
      +  "description": "true = render HTML tags in body.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person ID."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / subject
      Added value: +{
      +  "description": "Note title.",
      +  "type": "string"
      +}
    • removedInput schema / properties / userId
      Removed value: -{
      -  "description": "User ID who created the note",
      -  "type": "number"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "personId",
      -  "body"
      -]New value: +[
      +  "personId"
      +]
  2. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — nothing about whether a person lookup failure errors out, whether notes are deduplicated, or what is returned after creation, despite the tool being non-idempotent.

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?

A single front-loaded sentence with zero padding or redundancy. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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?

For a simple four-parameter create tool with full schema coverage and complete annotations, the description is minimally adequate. Gaps remain around what happens with an unknown personId and what the response contains (no output schema exists), which matters for a mutation.

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%, with body, isHtml, subject and personId each documented inline, so the schema carries the parameter meaning. The description adds nothing further — notably it does not clarify that body is optional while personId is required, which would have been useful for a create call.

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?

The description gives a specific verb and resource ('Create a note') plus the scope it attaches to ('on a person'), which is clearer than the bare name. It does not distinguish itself from siblings such as inboxAppAddNote or updateNote, so an agent still has to infer which note-creation path applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g., the person must already exist), and no mention of alternatives like inboxAppAddNote despite that sibling being present in the tool set. The agent is left to infer usage entirely.

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