Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listAutomations

Read-onlyIdempotent

List Follow Up Boss Automations 2.0 workflows and filter by status, enabled state, or manual trigger. Page through results to review available CRM automations.

Instructions

List Automations 2.0 automations. Needs registered-system credentials and Automations 2.0.

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

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 status.
manualOnlyNoOnly automations with a manual trigger. Default false.
enabledOnlyNoOnly enabled. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / enabledOnly
      Added value: +{
      +  "description": "Only enabled. Default false.",
      +  "type": "boolean"
      +}
    • 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 / manualOnly
      Added value: +{
      +  "description": "Only automations with a manual trigger. Default false.",
      +  "type": "boolean"
      +}
    • 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"
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Filter by status.",
      +  "enum": [
      +    "Active",
      +    "Disabled",
      +    "Deleted"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds a real behavioral constraint beyond that — the requirement for registered-system credentials and the Automations 2.0 feature — which is useful context an agent cannot get from annotations. It says nothing about return shape, pagination behavior, or failure modes.

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 the resource named first and the prerequisite second; nothing is wasted. It is terse to the point that the prerequisite sentence is almost telegraphic, which slightly limits readability.

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 read-only list tool with fully documented parameters and no output schema, the definition covers purpose and gating requirements. It omits any indication of what is returned (e.g., automation fields, metadata.next cursor semantics) and gives no fallback guidance if the Automations 2.0 prerequisite is unmet.

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%, with all six parameters documented including the cursor/offset paging preference and enum values for status. The description adds no meaning beyond the schema, 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?

States a clear verb+resource: 'List Automations 2.0 automations', and the '2.0' qualifier helps separate it from legacy automation siblings like getAutomation. It does not explicitly distinguish itself from listAutomationsPeople, but the object being listed 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 Guidelines3/5

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

The description gives prerequisites ('Needs registered-system credentials and Automations 2.0') but no explicit when-to-use or when-not-to-use guidance relative to siblings such as getAutomation or listAutomationsPeople. Usage is only implied by the word 'List'.

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