Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_contact_delete_from_workflow

DestructiveIdempotent

Removes a contact from a specific GoHighLevel workflow by contact ID and workflow ID. Use it to stop automated messages and actions for a contact without deleting the contact.

Instructions

Delete Contact from Workflow Endpoint: DELETE /contacts/{contactId}/workflow/{workflowId} (Version header: v3; source: v3/contacts-v3.json) OAuth scopes: contacts.write

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": {
      "contactId": "<contactId>",
      "workflowId": "<workflowId>",
      "body": "<body>"
    },
    "name": "ghl_contact_delete_from_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
contactIdYesContact Id
workflowIdYesWorkflow Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateWorkflowDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried. The description adds genuinely useful context in the OAuth scope (contacts.write) and API version header. However, it never clarifies the scope of deletion – whether it removes only the workflow enrollment or affects the contact record itself, which is exactly the concern destructiveHint raises.

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?

Three short lines, with the operation name front-loaded before the endpoint and auth metadata. Slightly boilerplate (source file path) but nothing wasteful enough to penalize heavily.

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?

For a destructive, 3-parameter tool with a nested body and no output schema, the description covers auth and endpoint but omits outcome semantics – what is removed, whether the contact record survives, and what a successful response confirms. Adequate minimum, with clear gaps.

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 contactId, workflowId, and the body object are already documented in the schema. The endpoint line reinforces the two path parameters but the nested body (eventStartTime) is left entirely to 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?

States a specific verb and resource ('Delete Contact from Workflow'), which is unambiguous and distinguishable from the sibling ghl_contact_add_to_workflow. It does not explicitly name the sibling, but the name and heading alone let an agent separate the two operations.

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?

There is no guidance on when to use this versus alternatives, no prerequisites (e.g., contact must currently be enrolled), and no mention of the add_to_workflow counterpart. The description gives endpoint and scope metadata but no decision context.

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