Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_webhook

Subscribes a secure HTTPS URL to receive real-time notifications for Follow Up Boss events, such as people created, deals updated, or notes deleted, enabling automated workflows.

Instructions

Subscribe to a new webhook. (POST /webhooks)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe url of the webhook. Must be a secure endpoint (https).
eventYesThe event the webook responds to. This should be one of the following: `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`, or `stageDeleted`
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It discloses the action ('subscribe') but does not describe side effects, idempotency, response behavior, or any requirements (e.g., authentication, rate limits). For a creating tool, this is a minimal disclosure.

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 extremely concise: 'Subscribe to a new webhook. (POST /webhooks)' – six words, front-loaded, with zero filler. It efficiently conveys the core action and endpoint.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and four parameters including open object fields (extraBody, extraQuery), this description is too sparse. It doesn't explain the response format, how to handle the extra raw fields, or any behavioral caveats, leaving the agent under-informed for correct invocation.

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%, and each parameter already has a descriptive schema definition. The tool description adds no parameter-level information, so the baseline of 3 is appropriate.

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 states a specific verb ('Subscribe') and resource ('new webhook'), and the HTTP method POST clarifies it is a creation endpoint. This clearly distinguishes it from siblings like update_webhook, list_webhooks, or get_webhook.

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 word 'new' implies this is for creating a webhook, and the sibling names suggest there are update/list/get variants. However, the description gives no explicit guidance on when to choose this over alternatives, no prerequisites, and no exclusions.

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