Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_task

Create a new task in Follow Up Boss CRM, specifying person, type, due date, and assignee to track follow-ups, calls, emails, and more.

Instructions

Create a new task. (POST /tasks)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the task.
typeNoType can be one of the following: `Follow Up`, `Call`, `Text`, `Email`, `Appointment`, `Showing`, `Closing`, `Open House` or `Thank You`
dueDateNoDue date for this task in YYYY-MM-DD format.
personIdYesThe id of the person this task is related to.
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
assignedToNoThe full name of the agent to assign this task. (Note: This is required if `assignedUserId` is empty.)
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.
dueDateTimeNoDue date for this task with a time included that also supports timezone suffixes. (e.g., 2004-11-16T03:00:00 -05:00)
isCompletedNoSets whether the task is completed or not.
assignedUserIdNoThe id of the user to assign to this task. (Note: This is required if `assignedTo` is empty.)
remindSecondsBeforeNoSet a reminder for the task to be sent via email and desktop notification. This is only available for tasks with a due time set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The description adds no behavioral insight beyond the name itself; it does not mention side effects, permissions, idempotency, or return behavior. With no annotations to fall back on, the description carries the full burden and fails to disclose anything not already obvious.

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?

The description is a single, direct sentence with no filler or repetition. It is compact and immediately comprehensible, fully earning its length.

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?

With 11 parameters, conditional requirements, and no output schema or annotations, the one-line description is insufficient for an agent to fully understand the tool's behavior and expected outcomes. The schema covers parameter details, but the description does not address return values or operational context.

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 parameters are fully documented within the input schema. The description itself contributes no additional parameter semantics, hitting the baseline for schema-heavy cases.

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

Purpose5/5

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

The description clearly states the action ('Create') and the resource ('a new task'), and includes the HTTP endpoint for additional precision. It is unambiguous and distinguishes itself from sibling tools like update_task, get_task, and list_tasks.

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?

No guidance is provided about when to use this tool versus alternatives, nor any exclusions or prerequisites. The description simply states what the tool does without context on when it is appropriate.

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