Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listWebhooks

Read-onlyIdempotent

Lists Follow Up Boss webhooks with optional filters by event type or status, supporting sort, limit, offset, and cursor pagination. Use it to audit or review registered webhooks.

Instructions

List webhooks. Account owner or registered system only. Filter by event or status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listWebhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call.
sortNoSort field. Default created
eventNoOnly webhooks for this event
limitNoResults to return. FUB default 10, max 100.
offsetNoRows to skip before results begin. Default 0.
statusNoOnly webhooks with this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • addedInput schema / properties / event
      Added value: +{
      +  "description": "Only webhooks for this event",
      +  "enum": [
      +    "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"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results to return. FUB default 10, max 100.",
      +  "type": "number"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before results begin. Default 0.",
      +  "type": "number"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort field. Default created",
      +  "enum": [
      +    "id",
      +    "created",
      +    "updated",
      +    "status",
      +    "event"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Only webhooks with this status",
      +  "enum": [
      +    "Active",
      +    "Disabled"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds a real behavioral fact not present in the annotations: the authorization requirement (account owner or registered system), which is exactly the kind of context that prevents a failed or forbidden call.

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?

Three short sentences with zero filler, front-loaded with the action and followed by the access constraint and the filter capability. Nothing is repeated and nothing could be removed without losing information.

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?

With six optional parameters and no output schema, the definition covers authorization and filtering but is silent on how cursor pagination (next) relates to offset/limit, which is the main ambiguity an agent faces on a list endpoint. It is adequate, not complete.

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 every parameter documented, enum'd, and defaulted (limit 10/max 100, offset default 0, sort default created, next cursor from _metadata.next). The description only restates filtering by event or status, adding no meaning beyond the schema, so the baseline 3 applies.

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?

"List webhooks" gives a specific verb and resource, and the addition of event/status filtering separates it from the single-record getWebhook sibling. It stops short of naming siblings explicitly, so an agent still infers the list-vs-get split rather than being told.

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?

"Account owner or registered system only" is a genuine applicability constraint that tells the agent when this call is even permitted, and the filter hint implies the enumeration use case. However, there is no explicit statement of when to prefer this over getWebhook or getWebhookEvents, and no exclusion guidance.

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