Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateWebhook

DestructiveIdempotent

Update an existing webhook's callback URL or event by ID; HTTPS URLs are required and access is limited to the account owner or registered system.

Instructions

Update a webhook. 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": {
      "id": "<id>"
    },
    "name": "updateWebhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook ID
urlNoCallback URL; must be https
eventNoEvent 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: -"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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is structured. The description adds the authorization requirement (account owner or registered system), which is real behavioral context not present in annotations. It stops short of saying what happens to fields that are omitted or whether an update is reversible.

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 the core action front-loaded and no filler. The https rule slightly duplicates the schema, but it is a one-clause constraint that does not bloat the definition.

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?

Adequate for a 3-parameter, fully documented tool with annotations and no output schema. The notable gap is that only id is required, yet the description never explains whether url/event are optional patches or whether omitted fields are preserved, which matters for a destructive update.

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%, so baseline is 3. The description's "url must be https" merely restates the schema's own constraint, and nothing is said about the partial-update semantics of id vs url vs event, which is where description-level meaning would add value.

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?

Names a specific verb+resource ("Update a webhook"), which cleanly distinguishes it from createWebhook, getWebhook and listWebhooks in the sibling set. It does not explicitly call out those siblings, but the verb alone is enough to pick it.

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" gives a concrete permission prerequisite that helps an agent decide whether the call can succeed. There is no explicit when-to-use-this-vs-createWebhook/getWebhook guidance, so usage is implied rather than stated.

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