Skip to main content
Glama
Sign In
Ethora MCP Server

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update App

ethora-app-update
DestructiveIdempotent

Update selected fields on an owned Ethora app—name, domain, tagline, color, or bot status—while leaving omitted fields unchanged.

Instructions

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 mutable fields on an app the caller owns (displayName, domainName, appTagline, primaryColor, botStatus). Partial update - omitted fields are left unchanged. Requires: an appId from ethora-app-list or ethora-app-create. Auth: user-auth mode, active session; the caller must own the app. Errors: 401 not logged in; 403 not owner; 404 unknown appId; 422 validation (e.g. domainName taken, primaryColor not #RRGGBB).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ethora-app-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNo24-char hex ObjectId of the app to update. Optional — defaults to the app most recently passed to `ethora-app-select`.
botStatusNo`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update`); `off` disables it. Does not change the bot's configured prompt or sources.
appTaglineNoShort tagline shown on the public app landing page.
domainNameNoSubdomain to host the web app at. Setting `abcd` makes the web app available at `abcd.ethora.com`. Must be unique across all Ethora apps; lower-case alphanumerics and dashes only.
displayNameNoNew human-readable app name. Visible in the app picker and on the public landing page.
primaryColorNoPrimary brand color in hex `#RRGGBB` format (e.g. `#F54927`). Used throughout the app UI.
appDescriptionNoDeprecated alias for `appTagline`, kept so older callers keep working. Prefer `appTagline`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv26.11.0
    • changedInput schema / properties / botStatus / description
      Previous value: -"`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update-v2`); `off` disables it. Does not change the bot's configured prompt or sources."New value: +"`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update`); `off` disables it. Does not change the bot's configured prompt or sources."
  2. Changed8 schema fields changedv26.9.3
    • changedInput schema / properties / appDescription / description
      Previous value: -"Set the application description"New value: +"Deprecated alias for `appTagline`, kept so older callers keep working. Prefer `appTagline`."
    • changedInput schema / properties / appId / description
      Previous value: -"appId for app"New value: +"24-char hex ObjectId of the app to update. Optional — defaults to the app most recently passed to `ethora-app-select`."
    • addedInput schema / properties / appTagline
      Added value: +{
+  "description": "Short tagline shown on the public app landing page.",
+  "type": "string"
+}
    • changedInput schema / properties / botStatus / description
      Previous value: -"Set the bot status to on or off, if on bot is enabled"New value: +"`on` enables the AI bot for new conversations (requires a configured prompt — see `ethora-bot-update-v2`); `off` disables it. Does not change the bot's configured prompt or sources."
    • changedInput schema / properties / displayName / description
      Previous value: -"displayName of the application"New value: +"New human-readable app name. Visible in the app picker and on the public landing page."
    • changedInput schema / properties / domainName / description
      Previous value: -"If the domainName is set to 'abcd', your web application will be available at abcd.ethora.com."New value: +"Subdomain to host the web app at. Setting `abcd` makes the web app available at `abcd.ethora.com`. Must be unique across all Ethora apps; lower-case alphanumerics and dashes only."
    • changedInput schema / properties / primaryColor / description
      Previous value: -"Set thie color of the application in #F54927 format"New value: +"Primary brand color in hex `#RRGGBB` format (e.g. `#F54927`). Used throughout the app UI."
    • removedInput schema / required
      Removed value: -[
-  "appId",
-  "botStatus"
-]
  3. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description goes well beyond them: it warns that previous values are not kept and cannot be restored from the API, clarifies the partial-update semantics (omitted fields unchanged), and enumerates auth mode plus concrete error codes (401/403/404/422) with a validation example. This is exactly the extra context annotations cannot carry.

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

Conciseness4/5

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

Front-loads the destructive warning, then the field list, then requirements/auth/errors — a sensible ordering for a mutation tool. Some content (error codes, per-field format rules) duplicates the schema, which is mild redundancy rather than bloat.

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

Completeness5/5

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

For a 7-parameter mutation with no output schema and no required fields, the description covers irreversibility, partial-update behavior, ownership requirement, auth mode, and failure modes. Nothing an agent needs to invoke this safely is missing.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema, including the botStatus vs. prompt distinction and the appDescription deprecation note. The description's field list largely restates that; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Update mutable fields on an app the caller owns') and enumerates exactly which fields are mutable (displayName, domainName, appTagline, primaryColor, botStatus). The scope is distinct from siblings like ethora-app-create and ethora-app-list, so an agent can route without opening the schema.

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?

Gives real usage context: confirm changes with the user first, and the `appId` must come from `ethora-app-list` or `ethora-app-create`. It also acknowledges the implicit app from `ethora-app-select`. It stops short of an explicit when-not or a named alternative tool, so it is strong but not fully routing.

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

Deploy Server

Other Tools