Skip to main content
Glama

ethora-mcp-server

Update Agent

ethora-agent-update
DestructiveIdempotent

Overwrites the fields you pass; previous values are not kept and cannot be restored from the API, so confirm changes to the prompt, name or settings with the user first. Update a saved AI agent (PUT /v2/agents/:agentId). All fields are optional - only what you pass is updated. Common uses: tune the system prompt after a test run, switch responseMode to control turn-taking in multi-agent rooms, or adjust cooldownSec. See ethora-agents-quickstart prompt for the end-to-end recipe. Requires: an agent id or address from ethora-agent-list or ethora-agent-create. Only the agent's owner can update it: a public agent from someone else, including the platform's Support Agent, answers 403, so ethora-agent-clone it and update the copy.

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name. For multi-agent scenarios prefer single-word names — the @-mention matcher uses exact display-name match with word-boundary.
slugNoURL-safe slug.
isRAGNoEnable RAG retrieval.
promptNoUpdated system prompt (persona + behaviour). For multi-agent rooms instruct the agent to end every message with an @-mention of the next speaker — that's how turn-handoff works through the response gate.
agentIdNoMongo _id (24 hex chars) of the agent to update.
ragTagsNoRestrict the bot's knowledge to sources carrying at least one of these tags; `[]` removes the restriction.
summaryNoShort bio.
triggerNoLegacy trigger field. Prefer `responseMode`.
llmModelNoLLM model override.
flowsYamlNoDeterministic scripted conversation for this agent, as YAML. Drives the agent through a fixed sequence (opening menu, appointment request, intake questionnaire, survey) instead of leaving every turn to the model. Compiled and validated server-side on save: an invalid script is rejected with code `FLOWS_INVALID` and per-line details, and nothing is stored. A flow named `start` is reserved and fires when a conversation opens. Buttons are authored here (`buttons:` on a `say` step, or `options:` on an `ask` step). Call `fetch` with id `doc:agent-flows` for the full authoring format before writing one. Pass an empty string to clear the script.
categoriesNoDirectory categories, any of: `customer-support` (customer-facing assistants), `persona` (a character or historical figure), `entertainment` (quizzes, games, scenarios), `worker` (internal work). Used to filter `ethora-agent-list`. Replaces the agent's current set.
visibilityNo'private' or 'public' (cross-app invitable).
cooldownSecNoMinimum seconds between this agent's replies in a given room. Damped 2x for bot-to-bot. Set 0 for quick turn-taking.
isPublishedNoConvenience alias for visibility='public'.
llmProviderNoLLM provider override.
botAvatarUrlNoAvatar image URL.
responseModeNoWhen the agent replies. 'always' = every message; 'mentioned' = only @-mention or /bot (best for multi-agent turn-taking); 'smart' = mini-LLM decides; 'probability' = coin-flip using `responseProbability`.
botDisplayNameNoDisplay name in chat UI.
greetingMessageNoMessage the agent posts when it first joins a new room.
agentIdOrAddressNoAlias for `agentId` - either name is accepted, pass whichever you have.
responseProbabilityNoIf responseMode='probability', odds (0-1) of replying. Damped 0.6x for bot-to-bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ragTags / description
      Previous value: -"RAG tag filter."New value: +"Restrict the bot's knowledge to sources carrying at least one of these tags; `[]` removes the restriction."
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.