Send an email to a contact in GoHighLevel CRM by providing contact ID, subject, and body. Supports up to 5000 characters and returns response in markdown or JSON.
Send email
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Email body (max 5000 chars) | |
| subject | Yes | Email subject | |
| contact_id | Yes | Contact ID | |
| response_format | No | Response format | markdown |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose behavioral traits such as side effects, permissions, or that it sends an email (a mutation). Only the basic action is stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short (two words) but under-specified for a tool with 4 parameters. It is not appropriately sized; it lacks essential details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given it is a mutation tool with 4 parameters and no output schema, the description is wholly incomplete, missing behavior, return information, and prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all parameters are described in the schema. The description adds no extra meaning beyond what the schema provides, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Send email' clearly states the action and resource, but it does not distinguish from the sibling 'send_sms' or specify scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like send_sms, or any prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lehr007-coder/gohighlevel-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server