Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Manage webhooks

manage_webhooks

List available webhook event types, retrieve existing webhooks, and create, update, or delete webhook subscriptions for FastBound.

Instructions

List available webhook event types, get a webhook, or create/update/delete a webhook subscription. action=list_events|get reads; create|update|delete are writes (require FASTBOUND_ALLOW_WRITES). For create provide name, url, and events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHTTPS endpoint URL (for create/update).
nameNoWebhook name (required for get/create/update/delete).
actionYes
eventsNoEvent names to subscribe to (see action=list_events).
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the account.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With only openWorldHint in annotations, the description carries the behavioral burden. It usefully classifies which actions are writes and the permission requirement, but it does not disclose side effects, idempotency, whether delete is destructive, or how updates behave. This is adequate but not rich.

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?

Two tight sentences front-load the full action set, immediately mark read vs write, and highlight the create parameter requirements. No filler or repetition of schema details.

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 multi-action tool with seven parameters and no output schema, the description covers action semantics, permissions, and create requirements. It could add more about update/delete semantics or side effects, but the core information needed to select and invoke the tool is present.

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 71%, and the schema already documents most parameters. The description adds value by saying create needs name, url, and events, but it does not explain the description parameter or further disambiguate action-specific requirements beyond what the schema states.

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 names the resource (webhooks) with concrete verbs: list event types, get, create, update, delete. It also distinguishes read actions from write actions, so an agent can immediately understand the tool's scope even without opening the schema.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear action-level guidance: reads are list_events/get, writes are create/update/delete, and writes require FASTBOUND_ALLOW_WRITES. It also states the required parameters for create. It does not mention alternatives because there are no webhook-specific siblings, so no when-not-to-use guidance is needed.

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