Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppInstall

Installs a Follow Up Boss inbox app for a user or account-wide; provide a published app ID and webhook subscription URL to receive replies.

Instructions

Install an inbox app for a user or account-wide. Needs the publishedInboxAppId from FUB's app catalog and a webhook subscriptionUrl for replies.

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": {
      "publishedInboxAppId": "<publishedInboxAppId>",
      "userId": "<userId>",
      "subscriptionUrl": "<subscriptionUrl>"
    },
    "name": "inboxAppInstall"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser ID to scope the app to, or 0 for account-wide.
subscriptionUrlYesWebhook URL that receives inbox app replies.
publishedInboxAppIdYesYour Published Inbox App ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / publishedInboxAppId / description
      Previous value: -"Published inbox app ID from FUB catalog"New value: +"Your Published Inbox App ID."
    • changedInput schema / properties / publishedInboxAppId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / subscriptionUrl / description
      Previous value: -"Webhook subscription URL"New value: +"Webhook URL that receives inbox app replies."
    • changedInput schema / properties / userId / description
      Previous value: -"User to install for"New value: +"User ID to scope the app to, or 0 for account-wide."
    • changedInput schema / properties / userId / type
      Previous value: -"number"New value: +"integer"
  2. Changed6 schema fields changedv1.1.3
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "App name",
      -  "type": "string"
      -}
    • addedInput schema / properties / publishedInboxAppId
      Added value: +{
      +  "description": "Published inbox app ID from FUB catalog",
      +  "type": "number"
      +}
    • addedInput schema / properties / subscriptionUrl
      Added value: +{
      +  "description": "Webhook subscription URL",
      +  "type": "string"
      +}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "App URL",
      -  "type": "string"
      -}
    • addedInput schema / properties / userId
      Added value: +{
      +  "description": "User to install for",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "url"
      -]New value: +[
      +  "publishedInboxAppId",
      +  "userId",
      +  "subscriptionUrl"
      +]
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false and importantly idempotent=false; the description adds the useful external dependency that the ID comes from FUB's app catalog and that a webhook URL is required for replies. It does not explain what happens on repeated installs given the non-idempotent hint, nor what the response contains, so it adds context but not the behavior that matters most.

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 short sentences: the action and scope come first, prerequisites second. No filler or restatement of the name.

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 three-required-parameter mutation with no output schema, the agent still lacks the outcome of the call (what an installation returns) and the consequence of re-invoking on an already-installed app. The description covers inputs well but leaves the result side and non-idempotent behavior unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds provenance for publishedInboxAppId ("from FUB's app catalog") that the schema does not state. It also confirms the subscriptionUrl's purpose (receiving replies), reinforcing rather than merely repeating the schema.

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 ("Install an inbox app") plus the scope choice ("for a user or account-wide"), which distinguishes it from the read-only sibling listInboxAppInstallations. It does not explicitly name any sibling, but the action verb is unambiguous.

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?

The description supplies prerequisites (app catalog ID, webhook subscription URL) which implies when the tool is applicable, but never states when to choose this over alternatives or when not to install (e.g. app already installed). Usage is implied rather than guided.

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