Skip to main content
Glama

Update Bot

neuron_update_bot
Idempotent

Update an existing bot's configuration. Only provided fields are modified; omitted fields remain unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier (UUID) of the bot to update
nameNoNew display name for the bot
llmModelNoOpenRouter model ID (e.g., 'google/gemini-2.5-flash-lite', 'openrouter/auto')
metadataNoArbitrary metadata object stored with the bot. Replaces the entire metadata field — include ALL existing keys you want to keep. Known keys: 'communityExitFollowUp' (auto-DM users who leave watched groups — { enabled: boolean, groupJids: string[], message: string with {name} placeholder }), 'learningConfig' (self-learning from conversations — { enabled: boolean, folder: string, groupChats: string[], dmPhones: string[], useAdminPhones: boolean }), 'loadBalancing' (multi-channel round-robin — { enabled: boolean, strategy: string }), 'welcomeNewMembers' (fine-tune welcome behavior — { batchWindowSeconds: number, groupJids: string[] }). Additional custom keys are preserved as-is.
maxTokensNoMaximum number of tokens the bot can generate per response
assignmentNoOne-sentence role definition for the bot (max 2000 chars)
systemPromptNoNew system prompt defining the bot's behavior and personality
llmTemperatureNoTemperature parameter controlling response randomness (0 = deterministic, 2 = creative)
welcomeMessageNoWelcome message sent to new members joining groups the bot manages. Setting this field activates the batched welcome feature — new members are accumulated over a window (default 60s) and welcomed in a single message with @mentions. Set to null to disable.
fallbackMessageNoMessage sent when the bot cannot understand user input (max 2000 chars)
greetingMessageNoAutomatic greeting sent when a new conversation starts (max 2000 chars)
escalationPromptNoPrompt template used when escalating to a human agent (max 5000 chars)
responsibilitiesNoArray of responsibility descriptions defining what the bot handles
whatsappChannelIdNoUnique identifier (UUID) of the WhatsApp channel to associate with the bot

TDQS

A4.1/5.0
Behavior4/5

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

The annotation indicates idempotentHint=true, and the description reinforces this by explaining the partial update behavior ('only provided fields are modified'). This adds context beyond the annotations. No contradictions are present, though it doesn't detail auth requirements or rate limits.

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?

The description is a single concise sentence that immediately conveys the core purpose and key behavior. Every word is necessary, and it is front-loaded with the action. There is no unnecessary fluff.

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

Completeness3/5

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

The tool has 14 parameters, nested objects, and no output schema. The description is short and does not explain what the tool returns upon success or what errors may occur. Given the complexity, the description could provide more context about expected outputs or prerequisites, making it only adequately complete.

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, so the baseline is 3. The tool description does not describe individual parameters but provides an overall behavior context that helps interpret them. The schema already carries the parameter documentation burden, so no additional value is added by the description.

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

Purpose5/5

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

The description states 'Update an existing bot's configuration,' which clearly identifies the action (update) and resource (bot configuration). It distinguishes from sibling tools like neuron_create_bot or neuron_update_channel by specifying the exact resource being modified.

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

Usage Guidelines4/5

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

The description specifies that 'Only provided fields are modified; omitted fields remain unchanged,' which guides usage for partial updates. However, it does not explicitly mention when not to use the tool or provide alternatives like neuron_create_bot for creating new bots.

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.4/5.0
Disambiguation3/5

Most tools are clearly separated by resource type, but there is meaningful overlap in messaging entry points (send_message, send_whatsapp, compose_message, bot_api_send) and contact ingestion/sync tools (import_contacts, populate_contacts, sync_whatsapp_contacts). The descriptions help disambiguate, but with 309 tools an agent will frequently need to read closely to pick the right one.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent verb_noun snake_case pattern: create_*, get_*, list_*, update_*, delete_*. Minor deviations like sales_stats, lead_stats, wallet_balance, and whoami break the pattern slightly, but overall naming is highly predictable.

Tool Count1/5

309 tools is an extreme count for any MCP server, even a broad platform. This creates significant cognitive load and navigation overhead for agents, and far exceeds the well-scoped 3-15 tool range where coherence is strongest.

Completeness4/5

The tool surface is remarkably comprehensive across bots, contacts, campaigns, flows, knowledge bases, personas, marketplace, wallet, and products. Minor gaps exist — lead sources lack update/delete tools, and there is no single get_task or get_webhook alongside their list/update/delete counterparts — but these are workable gaps rather than dead ends.

Resources