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

ghl-mcp-server-v2

by zackscriven

ghl_email_verify

Verifies an email address or contact ID through GoHighLevel and charges any verification fees to the specified sub-account location.

Instructions

Email Verification Verify Email Endpoint: POST /email/verify (Version header: v3; source: v3/email-isv-v3.json) Requires a Sub-Account (location) token. OAuth scopes: lc-email.readonly

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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_email_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id, The email verification charges will be deducted from this location (if rebilling is enabled) / company wallet

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact endpoint and version header, the sub-account/location token requirement, and the OAuth scope (lc-email.readonly). It does not disclose that the call incurs charges or what the response looks like, but the auth/scope disclosure is a real contribution.

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?

Four short lines, action stated first, followed by endpoint, auth and scope metadata. Compact, though the 'source: v3/email-isv-v3.json' provenance note is internal noise that does not help an agent.

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?

There is no output schema, and the description never says what a verification call returns — an agent calling it cannot know whether it gets a boolean, a deliverability verdict, or a contact check. Combined with the unmentioned per-call charge that the schema hints at, this is adequate but leaves a meaningful gap for a verification-style endpoint.

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 description coverage is 100% and the nested body (type enum email/contact, verify value) is fully documented in the schema, so the baseline is 3. The description adds only the implicit link between locationId and the sub-account token, which is marginal.

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 ('Verify Email') plus the concrete endpoint POST /email/verify, which distinguishes it from the ghl_email_* campaign/template tools in the sibling list. However it never says what verification actually produces (deliverability status? syntax check? contact lookup?), so the purpose is clear at the API-operation level but not at the outcome level.

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?

The description gives no when-to-use guidance, no alternatives, and no preconditions beyond 'requires a Sub-Account token'. The schema mentions that charges are deducted from the location, but the description itself offers nothing about when an agent should call this versus other email tools.

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