Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getWebhookEvents

Read-onlyIdempotent

Retrieve the delivery events for a Follow Up Boss webhook by ID, including event type, creation time, resource IDs, and URI. Use it to inspect webhook activity and troubleshoot deliveries.

Instructions

Get the events delivered for a webhook (id, eventCreated, event, resourceIds, uri). 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": {
      "id": "<id>"
    },
    "name": "getWebhookEvents"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds two things the annotations do not: the authorization constraint ('Account owner or registered system only') and the shape of the payload returned (id, eventCreated, event, resourceIds, uri), which matters since there is no output schema.

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?

One tight sentence with the purpose front-loaded and the returned fields grouped in a parenthetical. The field list earns its place because no output schema exists; nothing is redundant or padded.

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

Completeness4/5

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

For a one-parameter read tool, the definition covers purpose, access requirement, and return shape, which is most of what an agent needs. The remaining gap is volume/pagination behavior — no indication of whether delivery events are capped, ordered, or time-bounded, which matters for a potentially long log.

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 single parameter 'id' is documented as 'Webhook ID', so the schema carries the load. The description adds no extra meaning about the ID — no note on where to obtain it (e.g., from listWebhooks) or what happens with an invalid/foreign ID. Baseline 3 is appropriate.

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 ('Get the events delivered for a webhook') and enumerates the returned fields, which clearly separates it from getWebhook/listWebhooks (configuration) and listEvents (calendar/activity events). It stops short of naming a sibling explicitly, so differentiation is inferred from the resource wording rather than stated.

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?

Usage is implied by 'events delivered for a webhook' — an agent can infer this is the delivery-log read for an existing webhook. There is no explicit when-to-use/when-not guidance and no pointer to getWebhook when the agent actually wants webhook configuration rather than delivery history.

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