Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

conversation_ai_update_agent

Idempotent

Update a GoHighLevel Conversations AI agent by modifying its goal, mode, channels, wait time, and sleep settings to refine automated interactions.

Instructions

Update Agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoThe goal of the agent.
modeNoMode of operation for the agent, required if primary is enabled.
nameNoName of the agent.
agentIdYesConversations AI agent id
channelsNoChannels the agent can use.
waitTimeNoWait time before agent responds (max 5 for minutes, 300 for seconds).
isPrimaryNoIndicates if this agent is a primary agent.
sleepTimeNoDuration of sleep period (required if sleepEnabled is true). Set to null for indefinite sleep. (max 2880 for minutes, 172800 for seconds, 48 for hours)
personalityNoPersonality traits of the agent.
businessNameNoName of the business the agent represents.
instructionsNoInstructions for the agent.
sleepEnabledNoIndicates if sleep functionality is enabled.
waitTimeUnitNoUnit for wait time - SECONDS or MINUTES
sleepTimeUnitNoUnit of sleep time - HOURS, MINUTES, or SECONDS (required if sleepEnabled is true). Set to null for indefinite sleep.
respondToAudioNoAllow agent to respond to audio
respondToImagesNoAllow agent to respond to images
knowledgeBaseIdsNoArray of knowledge base IDs associated with this agent.
autoPilotMaxMessagesYesMaximum number of messages in auto-pilot mode before requiring human intervention. (max: 100, min: 1)
sleepOnManualMessageNoEnable sleep when a manual outbound message is sent.
sleepOnWorkflowMessageNoEnable sleep when a workflow outbound message is sent.
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a non-destructive write operation. The description adds no additional behavioral context such as side effects, permissions, or rate limits. It does not contradict the annotations.

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

Conciseness3/5

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

The description is extremely concise (two words), which is efficient but lacks any contextual structure. It does not front-load key information beyond the verb and object. While it avoids fluff, it is under-specified for a tool of this complexity.

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

Completeness2/5

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

Given 20 parameters and no output schema, the description is insufficiently complete. It does not explain what happens on success, error scenarios, or any behavioral nuances. The rich schema partially compensates, but more context is needed for an agent to use this tool correctly.

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 input schema has 100% description coverage for all 20 parameters, so the baseline is 3. The description adds no parameter-specific meaning, but the schema fully documents each field. The description does not need to compensate for any gaps.

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?

The description states a clear verb and resource: 'Update Agent'. However, it does not differentiate from sibling tools like conversation_ai_create_agent or conversation_ai_update_action. It is minimally descriptive but unambiguously indicates the action.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or exclusions. An agent must infer usage from the name alone.

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