Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

voice_ai_patch_agent

Update an existing GoHighLevel voice AI agent's configuration, adjusting voice, language, prompt, working hours, and call end notifications.

Instructions

Patch Agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesUnique agent identifier
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}"
locationIdNoLocation ID 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?

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a mutating but non-destructive operation. The description adds no behavioral context beyond the name, such as partial update semantics, required agent existence, or side effects. It does not contradict annotations, but it provides zero value in explaining behavior.

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?

The description is extremely concise, but it is under-specified rather than efficiently written. Two words that only repeat the tool name do not earn their place; they fail to convey functional meaning. It is not a structured description that aids comprehension.

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?

With 20 parameters and no output schema, a two-word description is wholly inadequate. An agent has no way to know what the tool does, what inputs matter, or what to expect as a result. The description is grossly incomplete for a tool of this complexity.

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%, with all 20 parameters fully described in the input schema. The description adds no parameter information, but per the baseline for high coverage, a score of 3 is appropriate. The schema does the heavy lifting here.

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

Purpose1/5

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

The description 'Patch Agent' is a tautology, essentially restating the tool name without providing a verb or resource context. It does not state that this modifies an existing voice AI agent via partial updates, nor does it distinguish itself from siblings like voice_ai_create_agent or voice_ai_update_action. The purpose is entirely unclear from this description alone.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this is the update path for existing agents, nor does it reference any preconditions or differences from create/delete/get operations. An agent selecting a tool would have no idea this is for patching an existing agent.

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