Skip to main content
Glama
Sign In
ActiveCampaign MCP

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_a_task_reminder

Create task reminders by providing the task ID and the interval in minutes to notify the assignee before the due date.

Instructions

🟡 WRITE · creates data · Task Notifications · POST /taskNotifications

Create a task reminder

Creates a new record. Not idempotent — calling twice may create duplicates.

Create a new task reminder

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body (application/json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

The description adds 'Not idempotent — calling twice may create duplicates,' which reinforces the idempotentHint in annotations. Beyond that, no additional behavioral traits (e.g., side effects, rate limits) are disclosed.

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?

The description contains repetition ('Create a task reminder' appears twice, and 'Create a new task reminder' is redundant). It includes an emoji and endpoint line, but could be more succinct.

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?

Given the simple parameter structure and high schema coverage, the description provides minimal context. It does not explain prerequisites (e.g., the task must exist) or what the response contains, though no output schema exists.

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?

The input schema already provides clear descriptions for both parameters (dealTask and interval) with 100% coverage. The tool description adds no extra context or meaning beyond what the schema offers.

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 clearly states 'Create a task reminder' and 'Creates a new record,' making the tool's purpose evident. However, it does not differentiate from sibling create tools like create_a_task, though the name itself provides some distinction.

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 on when to use this tool versus alternatives such as create_a_task or other reminder-related tools. There is no mention of prerequisites or context for usage.

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