Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

voice_ai_create_agent

Create a voice AI agent in GoHighLevel to automate inbound call handling, with customizable voice, language, working hours, and notification settings.

Instructions

Create Agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voiceIdNoIdentifier for the speech synthesis voice from available voice options. Default: Auto generated
languageNoLanguage code for the agent's speech and understanding. Default: "en-US"
timezoneNoIANA timezone identifier affecting working hours and scheduling. Default: Location timezone
agentNameNoDisplay name for the voice AI agent, between 1-40 characters. Default: "My Agent {random 3 digit number}"
locationIdNoUnique identifier for the location where this agent will operate Defaults to GHL_LOCATION_ID when omitted.
agentPromptNoCustom instructions defining the agent's behavior and personality. Default: Basic prompt generated automatically
translationNoLanguage translation settings including enablement flag and target language code. Rules: (1) translation.enabled can only be true if the agent's language is not en-US; (2) when enabled, translation.language must be either the agent's language or en-US; (3) when enabled, translation.language is requi
businessNameNoName of the business this agent represents. Default: Uses location name
numberPoolIdNoIdentifier for the number pool managing phone number allocation. Default: null
inboundNumberNoPhone number for receiving inbound calls to this agent. Default: null
patienceLevelNoTolerance level for caller response delays. Default: "high"
welcomeMessageNoInitial greeting spoken when the agent answers calls. Default: Auto generated
maxCallDurationNoMaximum call duration in seconds, between 180-900 (3-15 minutes). Default: 300 seconds (5 minutes)
agentWorkingHoursNoTime intervals defining when the agent accepts calls, organized by day of week. Default: [] (available 24/7)
callEndWorkflowIdsNoArray of workflow IDs to trigger automatically when calls end. Default: []
sendUserIdleRemindersNoEnables automatic reminders when callers are silent. Default: true
isAgentAsBackupDisabledNoPrevents this agent from being used as a fallback option. Default: false (Available as backup agent)
sendPostCallNotificationToNoConfiguration for post-call email notifications to various recipients. Default: []
reminderAfterIdleTimeSecondsNoSeconds to wait before sending idle reminders, between 1-20. Default: 8 seconds
Behavior1/5

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

With annotations only indicating basic flags (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), the description carries no additional behavioral context. It does not explain side effects, permissions, or what the creation actually entails, leaving agents blind to the operation's implications.

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

Conciseness2/5

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

While extremely brief, the description is under-specified rather than concise. It fails to convey any essential information, and this brevity undermines its utility. The two-word phrase is not an efficient summary but an empty placeholder.

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

Completeness1/5

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

Given 19 parameters, no output schema, and no behavioral disclosures, the description is completely inadequate. An agent has no information about return values, side effects, or how the response should be interpreted. This is a severe gap for a complex creation tool.

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 description coverage is 100%, with each of the 19 parameters having detailed descriptions. The description adds nothing, but benefiting from the schema's richness, the baseline of 3 is appropriate. It neither helps nor hinders parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create Agent' is essentially a restatement of the tool name, providing no detail beyond the verb and resource. It fails to distinguish from sibling tools like conversation_ai_create_agent or agent_studio_create_agent, making it a tautology rather than a clarifying statement.

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

Usage Guidelines1/5

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

The description contains no guidance on when to use this tool versus alternatives, nor any prerequisites or context. An agent has no indication of the appropriate scenario for invoking this tool, making the guidance entirely absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-ghl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server