Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createTask

Create a task on a Follow Up Boss contact and assign it to a user with a due date or time. Set the task type, reminder lead time, and completion status in one call.

Instructions

Create a task on a person. personId is required, and one of assignedUserId or assignedTo is required. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.

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

Input Schema

NameRequiredDescriptionDefault
nameNoTask name
typeNoTask category
dueDateNoDue date, YYYY-MM-DD
personIdNoPerson the task relates to
assignedToNoFull name of the user to assign
dueDateTimeNoDue date-time with optional offset, e.g. 2026-11-02T15:00:00-05:00
isCompletedNoMark completed or not
assignedUserIdNoUser ID to assign
remindSecondsBeforeNoReminder lead time in seconds; only for tasks with a due time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.0
    • addedInput schema / properties / assignedTo
      Added value: +{
      +  "description": "Full name of the user to assign",
      +  "type": "string"
      +}
    • changedInput schema / properties / assignedUserId / description
      Previous value: -"Assigned user ID"New value: +"User ID to assign"
    • changedInput schema / properties / dueDate / description
      Previous value: -"Due date ISO"New value: +"Due date, YYYY-MM-DD"
    • addedInput schema / properties / dueDateTime
      Added value: +{
      +  "description": "Due date-time with optional offset, e.g. 2026-11-02T15:00:00-05:00",
      +  "type": "string"
      +}
    • addedInput schema / properties / isCompleted
      Added value: +{
      +  "description": "Mark completed or not",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person the task relates to"
    • addedInput schema / properties / remindSecondsBefore
      Added value: +{
      +  "description": "Reminder lead time in seconds; only for tasks with a due time",
      +  "type": "number"
      +}
    • removedInput schema / properties / status
      Removed value: -{
      -  "description": "Task status",
      -  "type": "string"
      -}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Task category",
      +  "enum": [
      +    "Follow Up",
      +    "Call",
      +    "Email",
      +    "Text",
      +    "Appointment",
      +    "Showing",
      +    "Closing",
      +    "Open House",
      +    "Thank You"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[]
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds the key call-time constraints but says nothing about duplicate handling, assignment resolution failures, or what happens when both assignment fields are supplied.

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?

Three short clauses, each carrying a distinct constraint, with the required-field rules front-loaded. Nothing is repeated from the schema and no sentence is wasted.

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 9-parameter creation tool with no output schema, the description covers the essentials an agent needs to avoid an invalid call. It omits defaults for type/isCompleted and reminder applicability, which are covered or inferable from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine cross-field meaning the schema lacks: personId is effectively required even though the schema's required array is empty, and exactly one of assignedUserId or assignedTo must be supplied. It also disambiguates dueDate from dueDateTime, which the schema only hints at.

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 specific verb and resource ('Create a task') and scopes it to a person, which lets an agent place it among the create/list/get/update task family. It does not distinguish itself from neighboring creation tools such as createAppointment or createNote, so it falls short of a 5.

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?

Gives the conditions required to make a valid call (personId plus one of assignedUserId/assignedTo) and tells the agent to prefer dueDateTime when a specific time is needed. It offers no guidance on when to choose this tool over createAppointment or createNote, so usage context is only implied.

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