Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTeamInboxes

Read-onlyIdempotent

List team inboxes with their users, returning up to 100 per call; use the next cursor to fetch additional pages when available.

Instructions

List team inboxes with their users. Returns up to 100 per call; if _metadata.next is set, call again with next.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listTeamInboxes"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
      +}
  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 read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds useful pagination behavior: returns up to 100 per call and indicates continuation via _metadata.next. It does not describe ordering, authentication needs, or the full response shape beyond 'with their users.'

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 front-loaded sentences with zero waste. The pagination instruction is included only where it affects invocation.

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 simple read-only list with full annotation coverage and fully described parameters, the description covers the essential pagination behavior and notes that users are included. It leaves out ordering and response-field details, but no output schema exists and the tool's complexity is low, so it is largely complete.

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%, and the schema already documents next, limit, and offset in detail. The description repeats the 100-result cap and next-cursor usage but adds no meaning beyond the schema, so 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?

States a specific verb ('List') and resource ('team inboxes with their users'), making the operation clear. It does not explicitly distinguish itself from any sibling, but no sibling directly conflicts with this resource, so clarity is high.

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?

Provides pagination mechanics (max 100 per call, follow _metadata.next) but gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. Usage is implied by the tool name and list operation.

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