Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listSmartLists

Read-onlyIdempotent

List Follow Up Boss smart lists, returning classic lists by default and current UI lists when all is true, to inspect saved segments.

Instructions

List all smart lists. By default only classic FUB smart lists are returned. Pass all: true to also include smart lists created in the current FUB UI (otherwise modern smart lists are invisible).

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

Input Schema

NameRequiredDescriptionDefault
allNoReturn all smart lists from both FUB Classic and current FUB. Use this to see all user-created smart lists.
fub2NoReturn smart lists created in FUB's current UI. By default only classic smart lists are returned.
nextNoCursor for next page of results
limitNoMaximum number of results to return
offsetNoOffset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.2
    • addedInput schema / properties / all
      Added value: +{
      +  "description": "Return all smart lists from both FUB Classic and current FUB. Use this to see all user-created smart lists.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fub2
      Added value: +{
      +  "description": "Return smart lists created in FUB's current UI. By default only classic smart lists are returned.",
      +  "type": "boolean"
      +}
  2. First observedv1.1.1

TDQS

A3.9/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 description correctly spends its words elsewhere: the silent filtering of modern smart lists is exactly the kind of surprise an agent needs flagged. It adds nothing about pagination or result volume, which is a minor gap given the five parameters.

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 default behavior and the override. The trailing parenthetical ('otherwise modern smart lists are invisible') partially restates the preceding clause, so there is some redundancy.

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 read-only listing tool with fully documented parameters and safety annotations, the description covers the critical default-scope behavior. Pagination (limit/offset/next) is left entirely to the schema, which is acceptable since it is documented there.

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 description coverage is 100%, so the baseline is 3. The description reinforces the semantics of `all` (including modern lists vs. invisible otherwise) but adds little the schema does not already state, and leaves the relationship between `all` and `fub2` ambiguous.

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 names a specific verb and resource ('List all smart lists') and immediately adds the non-obvious default scope ('only classic FUB smart lists are returned'). It is clearly a list operation distinguishable from the sibling getSmartList, though it never names that sibling explicitly.

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?

Gives a concrete when-to-use rule: pass `all: true` when modern FUB UI smart lists must be included, with the consequence of omitting it spelled out. It does not address the `fub2` flag or when to use it versus `all`, which are overlapping alternatives the agent must still resolve.

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