Skip to main content
Glama

create_follow_up_task

Create a follow-up reminder for a person to get back to a contact. For work the team owes (checking a database, fixing a bug, a refund), use create_task instead. Creates persistent state and is NOT idempotent: calling it twice creates two reminders. Nothing is sent when it comes due — it is a to-do, not an automation; use send_message or a broadcast to actually message someone. It stays open until someone completes it: a reply from the contact does not close a reminder created here (only the automatic "no reply for N days" follow-ups close on a reply). Created with a personal API key it is assigned to that user; with a workspace key it lands unassigned. While leads are on for the workspace, a reminder about a person creates no follow-up: their lead is parked until dueAt instead (made a lead first if needed) and reasonText goes into the lead history; the result says so and has task null.

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": {
      "dueAt": "<dueAt>",
      "reasonCode": "<reasonCode>",
      "reasonText": "<reasonText>"
    },
    "name": "create_follow_up_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueAtYesRequired. When it should surface, ISO 8601 and in the future, e.g. "2026-09-12T09:00:00Z".
contactIdNoContact the reminder is about, as returned by list_contacts. Omit for a standalone reminder with no conversation behind it.
reasonCodeYesRequired. Short machine-readable slug for why, e.g. "pricing_question".
reasonTextYesRequired. One line a person will read when the reminder comes due.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses persistent state, duplicate reminders on repeated calls, the absence of automatic messaging, manual completion semantics, and assignment differences between personal and workspace keys. The detailed leads-enabled behavior, including lead parking and a null task result, is especially valuable for predicting side effects.

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?

The description front-loads purpose and the most important sibling alternative, then organizes behavioral caveats in a logical sequence. It is a long, dense paragraph, but nearly every sentence addresses a consequential behavior rather than adding filler.

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

Completeness5/5

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

For a complex, non-idempotent creation tool, it covers selection, side effects, lifecycle, authentication-dependent assignment, and the major conditional leads workflow. Although there is no output schema, it at least documents the important exceptional result in which task is null; the schema handles ordinary invocation details.

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 already 100%, but the description adds meaningful interactions among parameters: dueAt controls lead parking and reasonText enters lead history when leads are enabled. It also clarifies the contact-specific case without needing to repeat basic formats already documented in the schema.

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 opening sentence gives a specific action and resource: creating a follow-up reminder for a person to get back to a contact. It immediately distinguishes this from create_task, which handles work the team owes such as bug fixes or refunds.

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

Usage Guidelines5/5

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

It explicitly routes team work to create_task and actual outreach to send_message or a broadcast. It also clarifies that this tool creates a to-do rather than an automation, giving the agent concrete selection and non-selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.