Skip to main content
Glama
Sign In
ActiveCampaign MCP

ActiveCampaign MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_a_custom_field_relationship_to_lists

Idempotent

Unlink a custom field from lists by deleting the relationship, removing the association without deleting the field or lists.

Instructions

🟡 WRITE · unlinks records · Field Rels · DELETE /fieldRels/{fieldRelId}

Delete a custom field relationship to list(s)

Removes an association between records (e.g. untags a contact, removes it from a list/automation). Reversible — it does not delete the underlying records.

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": {
      "fieldRelId": "<fieldRelId>"
    },
    "name": "delete_a_custom_field_relationship_to_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldRelIdYesField relationship ID to be deleted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

The description adds useful behavioral context beyond annotations: it labels the operation as a WRITE, shows the HTTP method/endpoint, and explicitly states reversibility. No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).

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 is compact, using a structured format with emoji indicator, HTTP verb, and endpoint. Every sentence adds value, though the initial line could be slightly more streamlined. Overall, it's efficient and front-loaded.

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?

Given the simple nature of the tool (one parameter, no output schema), the description is fairly complete. It explains the action, its reversible nature, and provides an example. It could briefly mention that no return value is expected, but that is acceptable.

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 schema provides 100% coverage for the single parameter, describing it as 'Field relationship ID to be deleted'. The description does not add any additional meaning or clarification beyond the schema, meeting the baseline expectation.

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 deletes a custom field relationship to list(s), and provides an example of its effect (e.g., untagging a contact). While distinct from many siblings, it does not explicitly differentiate from other deletion tools, but the specificity is sufficient.

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 notes the operation is reversible and does not delete underlying records, giving context on when to use. However, it lacks explicit guidance on when not to use or alternatives, such as pointing to other update or delete tools for different scopes.

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