Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listPipelines

Read-onlyIdempotent

Lists Follow Up Boss pipelines and retrieves a pipeline by exact name, with limit, offset, and cursor controls for paged results.

Instructions

List pipelines, optionally by exact name.

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

Input Schema

NameRequiredDescriptionDefault
nameNoExact pipeline name to look up
nextNoCursor from _metadata.next of the previous call.
limitNoResults to return. FUB default 10, max 100.
offsetNoRows to skip before results begin. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results to return. FUB default 10, max 100.",
      +  "type": "number"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Exact pipeline name to look up",
      +  "type": "string"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before results begin. Default 0.",
      +  "type": "number"
      +}
  2. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/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 fully covered. Beyond that the description adds nothing behavioral — no mention of pagination behavior (even though next/limit/offset exist), result ordering, or what an empty name match returns.

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?

A single front-loaded sentence with zero filler and the optional filter stated immediately. Nothing in it is redundant, though the terseness shifts all detail onto the schema.

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 simple four-parameter paginated read with full schema coverage, rich read-only annotations, and no output schema, the definition is minimally sufficient. It is thin on pagination workflow (when to follow next vs use offset) and on result shape, which the schema alone does not teach.

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 all four parameters are already documented in the schema, including the exact-name semantics and the cursor's origin in _metadata.next. The description's "exact name" phrasing merely restates the schema rather than adding meaning, so the 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?

The description gives a specific verb and resource ("List pipelines") and notes the optional exact-name filter, so an agent knows this is the collection-level read operation. It does not explicitly distinguish itself from the sibling getPipeline (single-record fetch), but the list/get split is strongly implied.

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?

Usage is only implied: "optionally by exact name" suggests you can narrow to one pipeline by name, but it never says when to prefer this over getPipeline or why name must be exact. No exclusions, prerequisites, or alternative routing are stated.

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