Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createWebhook

Create a webhook that sends Follow Up Boss event notifications to an HTTPS callback URL, supporting one event per webhook for real-time CRM updates.

Instructions

Create a webhook for one event. url must be https. Account owner or registered system only.

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": {
      "event": "<event>",
      "url": "<url>"
    },
    "name": "createWebhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCallback URL; must be https
eventYesEvent the webhook fires on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / event / description
      Previous value: -"Webhook event type"New value: +"Event the webhook fires on"
    • addedInput schema / properties / event / enum
      Added value: +[
      +  "peopleCreated",
      +  "peopleUpdated",
      +  "peopleDeleted",
      +  "peopleTagsCreated",
      +  "peopleStageUpdated",
      +  "peopleRelationshipCreated",
      +  "peopleRelationshipUpdated",
      +  "peopleRelationshipDeleted",
      +  "notesCreated",
      +  "notesUpdated",
      +  "notesDeleted",
      +  "emEventsOpened",
      +  "emEventsClicked",
      +  "emEventsUnsubscribed",
      +  "tasksCreated",
      +  "tasksUpdated",
      +  "tasksDeleted",
      +  "appointmentsCreated",
      +  "appointmentsUpdated",
      +  "appointmentsDeleted",
      +  "textMessagesCreated",
      +  "textMessagesUpdated",
      +  "textMessagesDeleted",
      +  "callsCreated",
      +  "callsUpdated",
      +  "callsDeleted",
      +  "dealsCreated",
      +  "dealsUpdated",
      +  "dealsDeleted",
      +  "emailsCreated",
      +  "emailsUpdated",
      +  "emailsDeleted",
      +  "eventsCreated",
      +  "stageCreated",
      +  "stageUpdated",
      +  "stageDeleted"
      +]
    • changedInput schema / properties / url / description
      Previous value: -"Callback URL"New value: +"Callback URL; must be https"
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read, non-destructive, non-idempotent operation, so the agent knows it mutates and may duplicate. The description adds an authorization requirement (account owner / registered system), which is valuable context beyond annotations, but omits duplicate-handling behavior, webhook count limits, and what is returned — meaningful gaps for a non-idempotent create.

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?

Three short sentences with no filler, and the scope constraint is front-loaded. Slight ambiguity in 'for one event' (one webhook per event vs. each webhook fires on one event) keeps it from a 5.

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 two-parameter create with full schema coverage and an output schema absent by design, the description is close to sufficient. It still leaves the agent without duplicate-creation behavior or return details, which matter given idempotentHint=false.

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 coverage is 100% and the event enum is fully enumerated in the schema, so the schema carries the parameter burden. The description only restates the https URL constraint already present in the schema's url description, adding no new meaning.

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?

States a specific verb and resource ('Create a webhook') plus the scoping constraint that each webhook covers a single event, which distinguishes it from updateWebhook/listWebhooks. It does not explicitly name a sibling alternative, but the create semantics are unambiguous.

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 sentence 'Account owner or registered system only' acts as a prerequisite, which is useful selection guidance. However, there is no explicit when-to-use vs. updateWebhook guidance and no statement about whether multiple webhooks per event are permitted, so usage must be inferred.

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