Skip to main content
Glama

update_assistant

Idempotent

Update an existing assistant (partial). Only the fields you send are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAssistant ID to update
modeNo
nameNoDisplay name of the assistant (max 255 chars)
typeNoAssistant call direction
toolsNo
recordNo
fillersNo
timezoneNoIANA timezone, e.g. "Europe/Berlin"
tool_idsNo
voice_idNoVoice ID from get_voices
folder_idNoFolder to place the assistant in (one folder per assistant). See list_folders. Send null to remove.
label_idsNoLabel IDs to tag the assistant with (an assistant can carry multiple labels). See list_labels.
variablesNo
language_idNoPrimary language ID from get_languages
webhook_urlNo
llm_model_idNoRequired for mode=pipeline
max_durationNo
ringing_timeNo
speech_speedNo
ambient_soundNo
endpoint_typeNo
filler_configNo
system_promptNoSystem prompt defining behavior
initial_messageNoFirst message spoken at call start (max 200 chars)
llm_temperatureNo
phone_number_idNo
voice_stabilityNo
knowledgebase_idNo
post_call_schemaNo
voice_similarityNo
is_webhook_activeNo
wait_for_customerNo
knowledgebase_modeNo
voice_mail_messageNo
allow_interruptionsNo
min_interrupt_wordsNo
multimodal_model_idNoRequired for mode=multimodal/dualplex
reengagement_promptNo
tts_emotion_enabledNo
ambient_sound_volumeNo
chat_llm_fallback_idNo
endpoint_sensitivityNo
max_silence_durationNo
post_call_evaluationNo
end_call_on_voicemailNo
interrupt_sensitivityNo
reengagement_intervalNo
secondary_language_idsNoAdditional language IDs the assistant can speak
synthesizer_provider_idNo
transcriber_provider_idNo
turn_detection_thresholdNo
enable_noise_cancellationNo
conversation_ended_retriggerNo
include_recording_in_webhookNo
max_initial_silence_durationNo
conversation_ended_webhook_urlNo
send_webhook_only_on_completedNo
conversation_inactivity_timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
messageNo

TDQS

C2.9/5.0
Behavior3/5

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

Adds 'Only the fields you send are changed' which implies idempotency and no effect on omitted fields, complementing annotations (readOnlyHint false, idempotentHint true). However, does not disclose other behaviors like error handling or side effects.

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

Conciseness5/5

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

Single sentence, front-loaded, no redundant words. Maximally concise.

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?

Despite having output schema and 58 parameters, the description is too minimal. Does not mention complex constraints, conditional requirements, or expected output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (22%), and the description provides no parameter-level meaning. It does not compensate for undocumented parameters.

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?

Clearly states 'Update an existing assistant (partial)', specifying verb and resource. Distinguishes from create_assistant by 'existing' and 'partial'. However, does not explicitly differentiate from other update tools in siblings.

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 on when to use vs alternatives like create_assistant or other update tools. The description lacks any usage context or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Most tools target distinct resources and actions clearly (e.g., create_assistant vs create_campaign). However, there is some overlap like get_outbound_assistants vs get_assistants and list_all_phone_numbers vs get_phone_numbers, causing minor ambiguity.

Naming Consistency4/5

Tools follow a consistent verb_noun pattern with underscores (e.g., create_document, delete_label, get_voices). Only minor deviations exist, such as generate_ai_reply and list_all_phone_numbers, but overall the pattern is maintained.

Tool Count2/5

With 75 tools, the server is excessively large. Although the domain is broad (assistants, calls, messaging, etc.), the number of tools makes it difficult for agents to navigate and select the correct one, reducing coherence.

Completeness4/5

The tool set covers CRUD operations for most resources, plus webhooks, AI replies, and reference data fetching. Minor gaps exist (e.g., no delete_conversation, no attach phone number to assistant), but the surface is largely comprehensive for the platform's purpose.