Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Export App

ethora-app-export-v2
Read-onlyIdempotent

Export an Ethora app as a portable JSON or ZIP bundle for backup or migration. Select sections like chats, users, sources, and botInstances, then import the result into another environment.

Instructions

Export an App as a portable bundle (GET /v2/apps/:appId/export). format=json returns the bundle object directly. Use include to select sections (e.g. 'chats,users,sources,botInstances'). Feed the result to ethora-app-import-v2. Requires: a selected app (ethora-app-select) or an explicit appId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoRequired in B2B mode unless already selected via ethora-app-select.
formatNo
includeNoComma-separated sections to include, e.g. 'chats,users,sources,botInstances'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv26.9.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds meaningful detail beyond those annotations: the HTTP method, format-specific return behavior, and the include-section selection mechanism.

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 dense, purposeful sentences with no filler. The endpoint and core behavior are front-loaded, and the prerequisite is cleanly separated at the end.

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?

For a read-only export tool with no output schema, the description covers purpose, parameter semantics, prerequisite, and downstream composition with the import tool. The zip return behavior is not detailed, but the essential information an agent needs is present.

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 67%, and the description compensates by explaining the appId prerequisite, the format=json return behavior, and the include syntax with an example. All three parameters receive useful semantic guidance beyond raw schema names.

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: 'Export an App as a portable bundle' with an explicit GET endpoint. It also distinguishes itself from related tools by naming the import counterpart and clarifying format/include behavior.

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 clear usage conditions: requires a selected app or explicit appId, and instructs feeding the result to ethora-app-import-v2. It does not explicitly enumerate when-not-to-use alternatives, but the context is strong enough for an agent to proceed correctly.

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