Skip to main content
Glama
Sign In
ActiveCampaign MCP

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

enable_disable_event_tracking

Idempotent

Enables or disables event tracking for your ActiveCampaign account. Modifies the event tracking status via a single action.

Instructions

🟡 WRITE · updates data · Event Tracking · PUT /eventTracking

Enable/disable

Modifies an existing record in place. Idempotent.

Enable or disable event tracking

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body (application/json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare idempotentHint and no destructive behavior. Description adds 'Modifies an existing record in place. Idempotent.' which matches, but adds little beyond annotations. No disclosure of side effects or state implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

Description is repetitive: 'Enable/disable' appears twice, and '🟡 WRITE' metadata is mixed in. Could be condensed to one or two sentences without redundant phrases.

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 no output schema and a nested param, description covers basic operation but lacks response info or constraints. Adequate for a simple boolean toggle but not comprehensive.

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 has 100% coverage with description for 'enabled' field. The description does not add parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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 the tool enables/disables event tracking, which is distinct from sibling 'enable_disable_site_tracking'. However, the description is cluttered with metadata, and the purpose is not as crisp as it could be.

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 over alternatives like 'enable_disable_site_tracking' or 'retrieve_event_tracking_status'. No prerequisites or context provided.

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