Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

addPersonToAutomation

Adds a person to a Follow Up Boss automation using person ID and automation ID to enroll them in automated follow-up workflows.

Instructions

Add a person to an automation

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personId": "<personId>",
      "automationId": "<automationId>"
    },
    "name": "addPersonToAutomation"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID
automationIdYesAutomation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=false, and destructive=false, so the safety profile is covered, but the description adds no behavioral context. Critically, it never says whether adding a person enrolls them and immediately triggers automation actions (emails/SMS), or what happens on a duplicate add given the non-idempotent hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with zero padding, which is structurally clean, but the brevity is under-specification rather than economy. Nothing is front-loaded because there is nothing beyond the name restatement.

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

Completeness2/5

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

This is a mutation/enrollment tool with no output schema and no explanation of what the call returns, whether side effects fire, or how failures (person already added, invalid automation) surface. For a state-changing operation, the description is too thin to let an agent call it confidently.

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%, so both required parameters are documented in the schema (albeit tersely as 'Person ID' and 'Automation ID'). The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name almost verbatim ('Add a person to an automation' for addPersonToAutomation), giving a clear but minimal verb+resource pair. It says nothing to separate it from siblings such as addPersonToActionPlan, listAutomationsPeople, or updateAutomationPerson.

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?

There is no guidance on when to use this tool rather than addPersonToActionPlan or updateAutomationPerson, and no prerequisites (e.g., whether the person must not already be in the automation) are stated. The agent must infer usage entirely from the name.

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