Skip to main content
Glama
Sign In
ActiveCampaign MCP

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_a_task_outcome

Create an outcome for tasks by specifying a title and sentiment. Choose from Positive, Neutral, or Negative, and optionally disable.

Instructions

🟡 WRITE · creates data · Task Outcomes · POST /taskOutcomes

Create a task outcome

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

Create a new task outcome

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_outcome"
  }
}

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?

Annotations already indicate a write, non-idempotent operation. The description adds 'Not idempotent — calling twice may create duplicates', which aligns with annotations but doesn't disclose additional behaviors like authorization needs or 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats 'Create a task outcome' three times and includes unnecessary emoji/header lines. Could be more concise and front-loaded.

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?

Minimal description covers basic creation and idempotency but omits information about required fields (title and sentiment are required in the schema) and the response format (no output schema). Adequate for a simple tool but incomplete.

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 coverage is 100%, so baseline 3. The description adds no extra meaning for parameters; it only restates the tool's purpose. No value added beyond the schema.

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 outcome' and 'Creates a new record', effectively conveying the verb and resource. However, it does not differentiate from the sibling tool 'create_a_task_outcome_1'.

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 on when to use this tool versus alternatives (e.g., update or the sibling create tool). Missing context about prerequisites or scenarios.

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