Skip to main content
Glama

Create/update/delete a chatbot command

manage_chatbot_command
Destructive

Create, update, or delete chatbot commands. Use variables in messages, add aliases, set cooldowns, and control visibility on your commands page.

Instructions

Create, update, or delete a chatbot command (chatbot commands are unlimited on every plan). Names are slugified (lowercase, spaces become dashes). "message" is the chat reply and is required for create; it supports {{variables}}. Update merges only the fields you pass; delete refuses built-in system commands. Requires an up-to-date Lumia Stream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe command name (without the chat prefix), e.g. "socials".
actionYesWhat to do.
aliasesNoAlternate names that also trigger the command.
enabledNoWhether the command is enabled. Defaults to true on create.
messageNoThe chatbot reply text. Required for create; optional for update.
new_nameNoFor update: rename the command to this.
descriptionNoInternal description shown in the commands list.
cooldown_secondsNoCooldown between uses, in seconds.
show_in_commands_listNoShow it on your public lumiastream.com commands page.
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. Description adds behavioral details: slugification, merge-only update, and restricted deletion. No contradiction, but could mention more about response 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?

Three concise sentences covering purpose, key behaviors, and prerequisite. No wasted words.

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

Completeness4/5

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

Covers essential extra context given 9 parameters and no output schema. Could mention response format or success confirmation, but adequate for agent usage.

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

Parameters4/5

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

Schema coverage is 100%. Description enhances with slugification of name, message requirement for create, and merge behavior for update. Adds value beyond schema without repeating it.

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 explicitly states the tool creates, updates, or deletes a chatbot command with specific verb+resource. It mentions unlimited commands, distinguishing it from siblings like trigger_command.

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?

Provides clear usage context: slugification, required message for create, merge behavior for update, and delete refusal for built-in commands. Lacks explicit when-not-to-use, but covers key scenarios.

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/lumiastream/MCP'

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