Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTextMessages

Read-onlyIdempotent

Retrieve text messages from Follow Up Boss filtered by person, phone number, thread, shared inbox, or message ID. Use it to review SMS conversations tied to a contact or number.

Instructions

List text messages. FUB requires at least one filter: personId, phone, toNumber, fromNumber, threadId, sharedInboxId, groupTextId, participants or id.

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": "listTextMessages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoComma-separated message IDs
nextNoCursor from _metadata.next of the previous page.
limitNoResults per call. Default 10, max 100.
phoneNoFilter by phone
offsetNoRows to skip. Default 0. Prefer next for deep paging.
personIdNoMessages for this person.
threadIdNoFilter by thread ID
toNumberNoMessages sent to this number.
fromNumberNoMessages sent from this number.
groupTextIdNoFilter by group text
participantsNoComma-separated participants
sharedInboxIdNoFilter by shared inbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.0
    • changedInput schema / properties / fromNumber / description
      Previous value: -"Filter by source number"New value: +"Messages sent from this number."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results per call. Default 10, max 100."
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / next / description
      Previous value: -"Cursor for next page of results"New value: +"Cursor from _metadata.next of the previous page."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip. Default 0. Prefer next for deep paging."
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / personId / description
      Previous value: -"Filter by person ID"New value: +"Messages for this person."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / toNumber / description
      Previous value: -"Filter by destination number"New value: +"Messages sent to this number."
  2. Changed8 schema fields changedv1.1.3
    • addedInput schema / properties / fromNumber
      Added value: +{
      +  "description": "Filter by source number",
      +  "type": "string"
      +}
    • addedInput schema / properties / groupTextId
      Added value: +{
      +  "description": "Filter by group text",
      +  "type": "number"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Comma-separated message IDs",
      +  "type": "string"
      +}
    • addedInput schema / properties / participants
      Added value: +{
      +  "description": "Comma-separated participants",
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "description": "Filter by phone",
      +  "type": "string"
      +}
    • addedInput schema / properties / sharedInboxId
      Added value: +{
      +  "description": "Filter by shared inbox",
      +  "type": "number"
      +}
    • addedInput schema / properties / threadId
      Added value: +{
      +  "description": "Filter by thread ID",
      +  "type": "string"
      +}
    • addedInput schema / properties / toNumber
      Added value: +{
      +  "description": "Filter by destination number",
      +  "type": "string"
      +}
  3. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's job is to add operational context. It does so by disclosing an API-level validation rule that the schema does not express (required is empty, yet a filter is mandatory), which prevents failed calls. Sorting order and default paging behavior are left unstated.

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 sentences, front-loaded with the action and immediately followed by the constraint that governs invocation. The nine-item filter enumeration is slightly redundant with the schema but earns its place by defining the mandatory-filter rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter read-only list tool with full schema coverage, the only missing load-bearing information would be the required-filter constraint, and that is stated. Paging (next, limit, offset) is fully explained in the schema, so nothing an agent needs to call correctly is absent.

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 every parameter is documented in the schema itself. The description only re-lists the filter names to define the "at least one" rule; it adds no syntax, format, or precedence guidance (e.g., whether id overrides other filters) beyond what the schema provides. The baseline of 3 fits.

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 opens with a specific verb and resource ("List text messages"), which clearly separates it from getTextMessage and createTextMessage. It does not explicitly name those siblings or state the scope of what is returned, but the action 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 Guidelines4/5

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

It gives a hard precondition — at least one filter from an enumerated list must be supplied — which is the key thing an agent needs before calling. It stops short of saying when to prefer this over getTextMessage for a single message or which filter to pick for a given intent.

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