Skip to main content
Glama
Sign In
ActiveCampaign MCP

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_fieldvalue

Create a custom field value for a contact with specified contact ID, field ID, and value. This operation creates a new record and is not idempotent.

Instructions

🟡 WRITE · creates data · Field Values · POST /fieldValues

Create a custom field value

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

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body (application/json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false, and description reinforces that with explicit duplication warning. No contradictions. Adds behavioral context beyond annotations.

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

Conciseness5/5

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

Extremely concise: 3 lines covering action, endpoint, and key behavior (non-idempotent). Front-loaded with emoji and clear verb. No unnecessary words.

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

Completeness4/5

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

For a simple create tool with nested input and no output schema, the description is adequate. It covers purpose and idempotency, though it lacks details on response or prerequisites.

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 is 3. Description adds no additional meaning to parameters beyond what the schema already provides.

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 custom field value' and 'Creates a new record', with endpoint and write indication. However, it does not differentiate from closely related siblings like create_a_custom_field_value, which may cause confusion.

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

Usage Guidelines3/5

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

The description mentions non-idempotency and potential duplicates, but provides no guidance on when to use this tool versus the many other create tools among siblings.

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