Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listAutomationsPeople

Read-onlyIdempotent

Lists person-automation pairings in Follow Up Boss, with filters for person, automation, and run status plus cursor-based pagination.

Instructions

List person/automation pairings. Needs registered-system credentials.

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

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous page.
limitNoResults per call. Default 10, max 100.
offsetNoRows to skip. Default 0. Prefer next for deep paging.
statusNoFilter by run status.
personIdNoPairings for this person.
automationIdNoPairings for this automation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.0
    • changedInput schema / properties / automationId / description
      Previous value: -"Filter by automation"New value: +"Pairings for this automation."
    • changedInput schema / properties / automationId / type
      Previous value: -"number"New value: +"integer"
    • 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"
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous page.",
      +  "type": "string"
      +}
    • 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"New value: +"Pairings for this person."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Filter by run status.",
      +  "enum": [
      +    "Initial",
      +    "Running",
      +    "Paused",
      +    "Completed"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds the credential prerequisite, which is genuine auth context not in the annotations, but says nothing about ordering, result shape, or the cost of deep paging.

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 short sentences with zero filler, and the core purpose is front-loaded before the prerequisite. It is slightly under-specified rather than verbose, but nothing is wasted.

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?

With six optional pagination/filter parameters and no output schema, the definition is thin: it never explains what a "pairing" record contains or how the credential requirement is satisfied. The rich schema and annotations fill most of the gap, making it adequate but not 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 description coverage is 100%, including the status enum and the note to prefer next over offset, so the schema carries all parameter meaning. The description adds no additional semantics about how personId/automationId combine or whether filters are ANDed.

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?

"List person/automation pairings" gives a specific verb (list) and a concrete resource (person/automation pairings), which is more precise than the bare name. It stops short of distinguishing it from nearby siblings such as listActionPlansPeople or getAutomationPerson, so an agent still has to infer which pairing listing it needs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only guidance is a prerequisite ("Needs registered-system credentials"); there is no statement of when to use this versus listAutomations, getAutomationPerson, or the other pairing tools. No exclusions or alternatives are offered.

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