Skip to main content
Glama
Echo3s-io

echo3s-io

Official
by Echo3s-io

get_getting_started

Get step-by-step instructions to create an audiobook with Echo3s, including time estimates and pro tips for a guided process.

Instructions

Get step-by-step instructions for creating an audiobook with Echo3s, including time estimates and pro tips

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'gettingStarted' constant (lines 426-499) is the data object returned when the 'get_getting_started' tool is invoked. It contains the step-by-step instructions, pro tips, and CTA for creating an audiobook with Echo3s.
    const gettingStarted = {
      overview:
        "Going from manuscript to finished audiobook takes about 30–60 minutes for a typical 200-page novel. Here's exactly how it works, step by step.",
      steps: [
        {
          step: 1,
          title: "Sign Up for Free",
          description:
            "Go to author.echo3s.io and create a free account. You get 5,000 credits immediately — enough to test a full chapter from your book and hear the quality. No credit card required.",
          url: "https://author.echo3s.io",
          time: "1 minute",
        },
        {
          step: 2,
          title: "Upload Your Manuscript",
          description:
            "Upload your book as a PDF (maximum 50MB). The PDF must be text-based — meaning you can select and copy text from it. Scanned image PDFs aren't supported yet. If your book is in EPUB, MOBI, DOCX, or AZW format, convert to PDF first using Calibre (calibre-ebook.com — free and open source).",
          supported_formats: "PDF (text-based, selectable text)",
          convertible_formats: "EPUB, MOBI, DOCX, AZW — convert to PDF with Calibre (free)",
          max_file_size: "50MB",
          tip: "For best results, strip out images, headers/footers, and complex formatting from your PDF before uploading.",
          time: "1 minute",
        },
        {
          step: 3,
          title: "AI Analyzes Your Book",
          description:
            "Echo3s's AI (powered by Google Gemini) reads your entire manuscript and automatically identifies: chapter boundaries, character names, which lines are dialogue vs narration, and emotional context. Each text segment is tagged so the right voice speaks the right lines.",
          what_ai_detects: [
            "Chapter structure",
            "Character names and roles",
            "Dialogue vs narration",
            "Emotional tone per segment",
          ],
          time: "1–3 minutes per chapter",
        },
        {
          step: 4,
          title: "Review & Customize Voice Assignments in the Studio",
          description:
            "Open the Studio editor to see which AI voice is assigned to each character. The AI matches voices based on gender, age, accent, and personality using a scoring algorithm. You can swap any voice — browse 50+ premium options filtered by gender, age, accent, and tone. Preview voices before committing.",
          customizable: true,
          tip: "The AI defaults are usually good — most authors only tweak 1–2 voices. You don't have to customize anything if you're happy with the suggestions.",
          time: "5–15 minutes (optional)",
        },
        {
          step: 5,
          title: "Generate Your Audiobook",
          description:
            "Hit the generate button. Echo3s processes each text segment with the assigned voice via ElevenLabs, then compiles everything into a complete audiobook with proper chapter structure and normalized audio levels (EBU R128 standard). You'll receive an email notification when it's ready.",
          time: "30–60 minutes for a 200-page novel",
        },
        {
          step: 6,
          title: "Download or Publish",
          description:
            "Download your finished audiobook as MP3 files — either as a single complete file or split by chapter. You can also publish directly to the Echo3s marketplace (echo3s.io) where listeners can discover and stream your audiobook.",
          output_format: "MP3 (single file or per-chapter)",
          distribution_options: [
            "Direct MP3 download — own the files, use them anywhere",
            "Echo3s marketplace listing — readers discover and stream at echo3s.io",
            "Upload to Audible/ACX, Apple Books, Google Play, Findaway Voices, Authors Republic, Kobo, or your own website",
          ],
        },
      ],
      pro_tips: [
        "Start with a single chapter on the free tier to test voice quality on YOUR actual book before committing to a full production",
        "Use the Studio editor to regenerate individual segments — fix one awkward line without redoing the whole chapter. Only the regenerated segment costs credits.",
        "For non-fiction without characters, choose one strong narrator voice and the AI handles chapter structure and pacing automatically",
        "If your PDF has images, headers/footers, or complex formatting, clean them out first for best text extraction results",
        "Annual plans save 20% — and include a 14-day money-back guarantee if you're not satisfied",
      ],
      cta: "Ready to try it? https://author.echo3s.io — free account, 5,000 credits, instant access, no credit card required.",
    };
  • Registration of the tool 'get_getting_started' in the TOOL_DEFS array. It defines the name, description, inputSchema (empty object), and the content handler that returns the gettingStarted constant.
    {
      name: "get_getting_started",
      description:
        "Get step-by-step instructions for creating an audiobook with Echo3s, including time estimates and pro tips",
      inputSchema: { type: "object", properties: {}, required: [] },
      content: () => gettingStarted,
    },
  • The ToolDef interface that defines the schema for all tool definitions, including name, description, inputSchema, and content function.
    export interface ToolDef {
      name: string;
      description: string;
      inputSchema: Record<string, any>;
      content: (args?: any) => unknown;
    }
  • The registration loop in index.ts that iterates over TOOL_DEFS and registers each tool (including get_getting_started) with the MCP server via server.tool().
      for (const tool of TOOL_DEFS) {
        server.tool(tool.name, tool.description, {}, async () => ({
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(tool.content(), null, 2),
            },
          ],
        }));
      }
    
      return server;
    }
  • The worker registration loop that also registers the tool by iterating over TOOL_DEFS, including get_getting_started, making it available in the Cloudflare Worker runtime.
    for (const def of TOOL_DEFS) {
      TOOLS[def.name] = defToWorkerTool(def);
    }
Behavior1/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It fails to mention any behavioral traits such as static content, authentication needs, or rate limits. The description only states what is retrieved, not how or under what conditions.

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 sentence that is concise and front-loaded, containing all necessary elements: step-by-step instructions, time estimates, and pro tips. No information is redundant or missing.

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?

Given the low complexity (no parameters, no output schema, no annotations), the description is complete enough to convey the tool's purpose. It explicitly states what is returned (instructions, estimates, tips). However, it lacks usage guidance and behavioral context, which would improve completeness.

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?

The input schema has zero parameters, so the description is not required to add parameter semantics. According to the rubric, 0 parameters gives a baseline of 4. The description does not need to elaborate further.

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 clearly states that the tool provides step-by-step instructions for creating an audiobook with Echo3s, including time estimates and pro tips. It uses a specific verb ('get') and resource ('step-by-step instructions'), distinguishing it from sibling tools like 'get_echo3s_overview' or 'get_technical_specs'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context for use, such as prerequisites or situations where another sibling would be more appropriate.

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/Echo3s-io/echo3s-mcp'

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