Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getWebhook

Read-onlyIdempotent

Retrieve a specific Follow Up Boss webhook by its ID to inspect its configuration or verify registration; restricted to account owners and registered systems.

Instructions

Get a webhook by ID. 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": "getWebhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description does add genuinely new behavioral context by disclosing an authorization constraint (account owner or registered system only), but it says nothing about what happens on a missing/nonexistent ID or how errors surface.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is compact, though it packs an access restriction without elaboration.

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 simple read-only single-record getter with full schema coverage and no output schema, the description covers the essential action plus authorization. It is thin, however, on return shape expectations and not-found behavior, which an agent would still have to discover by calling it.

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% for the single `id` parameter, so the schema already documents it as a numeric "Webhook ID". The description adds no format, sourcing, or lookup-mechanics detail beyond what the schema provides, 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?

The description uses a specific verb and resource ("Get a webhook") and adds the retrieval key ("by ID"), so the agent knows this is a single-resource fetch rather than a listing. It does not distinguish itself from nearby siblings like getWebhookEvents or listWebhooks, which a reader must infer from name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 permission gate, not when-to-use guidance: it does not say when to call this versus listWebhooks or getWebhookEvents, nor what to do if the caller lacks ownership. There is no explicit exclusion or alternative routing.

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