Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTasks

Read-onlyIdempotent

Retrieve and filter Follow Up Boss CRM tasks by due date, assignee, contact, or completion status to find open, overdue, or upcoming work.

Instructions

List tasks. Use due=overdue for overdue tasks, due=today for today's, assignedUserId for one user's tasks, personId for one contact's. Add isCompleted=false for open tasks only. Filters combine.

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

Input Schema

NameRequiredDescriptionDefault
dueNoDue-date bucket
nameNoTasks whose name contains this text
nextNoCursor from _metadata.next of the previous call.
sortNoSort order
typeNoTask type; comma-separated list. Values: Follow Up, Call, Email, Text, Appointment, Showing, Closing, Open House, Thank You
limitNoResults to return. FUB default 10, max 100.
dueEndNoISO date-time; tasks due at or before this time
fieldsNoComma-separated fields to return
offsetNoRows to skip before results begin. Default 0.
dueStartNoISO date-time; tasks due from this time
personIdNoTasks for this person ID
assignedToNoTasks assigned to this user's full name
isCompletedNotrue = completed only, false = open only
assignedUserIdNoTasks assigned to this user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.0.0
    • addedInput schema / properties / assignedTo
      Added value: +{
      +  "description": "Tasks assigned to this user's full name",
      +  "type": "string"
      +}
    • addedInput schema / properties / assignedUserId
      Added value: +{
      +  "description": "Tasks assigned to this user ID",
      +  "type": "number"
      +}
    • addedInput schema / properties / due
      Added value: +{
      +  "description": "Due-date bucket",
      +  "enum": [
      +    "today",
      +    "overdue",
      +    "upcoming"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / dueEnd
      Added value: +{
      +  "description": "ISO date-time; tasks due at or before this time",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueStart
      Added value: +{
      +  "description": "ISO date-time; tasks due from this time",
      +  "type": "string"
      +}
    • changedInput schema / properties / fields / description
      Previous value: -"Comma-separated list of fields to return"New value: +"Comma-separated fields to return"
    • addedInput schema / properties / isCompleted
      Added value: +{
      +  "description": "true = completed only, false = open only",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results to return. FUB default 10, max 100."
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Tasks whose name contains this text",
      +  "type": "string"
      +}
    • changedInput schema / properties / next / description
      Previous value: -"Cursor for next page of results"New value: +"Cursor from _metadata.next of the previous call."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip before results begin. Default 0."
    • addedInput schema / properties / personId
      Added value: +{
      +  "description": "Tasks for this person ID",
      +  "type": "number"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Task type; comma-separated list. Values: Follow Up, Call, Email, Text, Appointment, Showing, Closing, Open House, Thank You",
      +  "type": "string"
      +}
  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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The one genuine behavioral addition is 'Filters combine', which tells the agent the predicates are ANDed rather than mutually exclusive. It says nothing about result-set size, pagination termination, or default ordering beyond what the schema states.

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?

Front-loaded with the purpose, then filter recipes in one compact paragraph with no filler. The clause 'due=overdue for overdue tasks, due=today for today's' is mildly circular — it restates the enum rather than explaining the boundary — but the rest of the sentence does real work.

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 14 optional parameters, no output schema, and a server-side default limit of 10, pagination is the most consequential thing an agent can get wrong, and the description never mentions that results are capped or that 'next' from _metadata must be followed. Filtering is well covered and annotations carry the safety story, so the omission is the main gap rather than a wholesale failure.

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 description coverage is 100%, so the baseline is 3, but the description earns an increment: it explains the semantics of the otherwise bare 'Due-date bucket' enum ('overdue' means overdue tasks) and, more importantly, disambiguates assignedUserId (a user) from personId (a contact) — a distinction the schema alone does not make. It does not clarify next/limit/offset paging or sort.

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?

The description opens with a specific verb+resource ('List tasks'), which cleanly separates it from the createTask/getTask/updateTask siblings whose verbs are explicit. It does not name those siblings directly, but the list-vs-single-record distinction is unambiguous from the tool names.

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

Usage Guidelines4/5

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

It gives concrete routing guidance for the main filter axes: due=overdue for overdue, due=today for today's, assignedUserId for one user, personId for one contact, and isCompleted=false for open-only. It lacks any statement about when to prefer getTask for a single record or when not to use this tool, so it stops short of a 5.

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