Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listInboxAppInstallations

Read-onlyIdempotent

Lists installations of a published inbox app for a registered third-party system, with pagination controls to retrieve and page through results.

Instructions

List installations of one published inbox app. Needs a registered third-party system (FUB_SYSTEM and FUB_SYSTEM_KEY).

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>"
    },
    "name": "listInboxAppInstallations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call for the next page.
limitNoResults per call, max 100. Server sends 100 when omitted (FUB's own default is 10).
offsetNoRows to skip before returning results.
publishedInboxAppIdYesPublished Inbox App ID whose installations to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results per call, max 100. Server sends 100 when omitted (FUB's own default is 10).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call for the next page.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before returning results.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / publishedInboxAppId
      Added value: +{
      +  "description": "Published Inbox App ID whose installations to list.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "publishedInboxAppId"
      +]
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds a real behavioral prerequisite beyond the structured fields: the call only works when a third-party system is registered via FUB_SYSTEM and FUB_SYSTEM_KEY, which an agent would not otherwise know.

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, front-loaded with the operation and immediately followed by the prerequisite. No filler or redundant restatement of the tool name.

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 paginated read tool with full schema coverage, annotations covering the safety profile, and no output schema, the description supplies the essentials plus the credential prerequisite. It stops short of describing what an installation record contains, but that is a minor gap.

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%, with next, limit, offset, and publishedInboxAppId all documented in the schema, so the baseline is 3. The description adds no extra detail about parameter format or interactions beyond what the schema already provides.

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 states a specific verb and resource ('List installations of one published inbox app'), which is clear and distinguishable from the sibling inboxAppInstall (which performs an install rather than listing). It does not explicitly name a sibling to route against, but the scope 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 implies usage by requiring a single publishedInboxAppId and notes a prerequisite (a registered third-party system with FUB_SYSTEM and FUB_SYSTEM_KEY). It gives no explicit when-to-use versus alternatives guidance or case where this tool should not be used.

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