# add_lead_comment (/docs/mcp/tools/add-lead-comment)

{/* Generated by scripts/sync-mcp-tools.mjs from happierleads-api. Do not edit: change src/routes/mcp/toolDocs.json there, or add content/mcp-notes/add_lead_comment.mdx. */}

**Add a comment to a lead** · Changes data

Add a note to a lead, visible to everyone on the account's team, signed with the connected user's name. leadId comes from get_leads. Read existing notes with get_lead_comments; edit with update_lead_comment. Each call adds a new comment. Returns status 'Successful' and commentId.

| Connection | Account URL, team member URL or OAuth |
| --- | --- |

## Parameters [#parameters]

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `leadId` | `string` | Yes | Lead id (the _id of a row returned by get_leads). |
| `content` | `string` | Yes | The comment text (plain text). |

## Tool definition [#tool-definition]

What your assistant receives from `tools/list`:

```json
{
  "name": "add_lead_comment",
  "title": "Add a comment to a lead",
  "annotations": {
    "title": "Add a comment to a lead",
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false,
    "openWorldHint": false
  },
  "inputSchema": {
    "type": "object",
    "properties": {
      "leadId": {
        "type": "string",
        "description": "Lead id (the _id of a row returned by get_leads)."
      },
      "content": {
        "type": "string",
        "description": "The comment text (plain text)."
      }
    },
    "required": [
      "leadId",
      "content"
    ]
  }
}
```