Skip to main content
Glama
Echo3s-io

echo3s-io

Official
by Echo3s-io

get_social_links

Retrieve all Echo3s links including website, blog posts, landing pages, and contact information.

Instructions

Get all Echo3s links — website, blog posts, landing pages, and contact information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `socialLinks` constant contains the data payload for the get_social_links tool — includes website URLs, blog posts, landing pages, and audiobook categories.
    const socialLinks = {
      links: {
        website: "https://echo3s.io",
        author_portal: "https://author.echo3s.io",
        pricing: "https://echo3s.io/pricing",
        blog: "https://echo3s.io/blog",
        about: "https://echo3s.io/about",
        email: "hello@echo3s.io",
      },
      blog_posts: [
        {
          title: "How to Convert PDF to Audiobook with AI",
          url: "https://echo3s.io/blog/how-to-convert-pdf-to-audiobook-with-ai",
        },
        {
          title: "5 Best AI Tools to Convert PDF to Audiobook in 2026",
          url: "https://echo3s.io/blog/best-ai-tools-convert-pdf-to-audiobook-2026",
        },
        {
          title: "How to Convert Any Book to Audiobook Using AI",
          url: "https://echo3s.io/blog/convert-book-to-audiobook-ai",
        },
        {
          title: "Echo3s vs ElevenLabs vs Speechify: Full Comparison",
          url: "https://echo3s.io/blog/echo3s-vs-elevenlabs-vs-speechify-comparison",
        },
        {
          title: "The Complete Guide to AI Audiobook Generation in 2026",
          url: "https://echo3s.io/blog/complete-guide-ai-audiobook-generation-2026",
        },
        {
          title: "How I Built a SaaS in 3 Months with Claude AI",
          url: "https://echo3s.io/blog/how-i-built-saas-3-months-claude-ai",
        },
      ],
      landing_pages: [
        {
          title: "PDF to Audiobook",
          url: "https://echo3s.io/pdf-to-audiobook",
          keyword: "pdf to audiobook",
        },
        {
          title: "Book to Audiobook Converter",
          url: "https://echo3s.io/book-to-audiobook",
          keyword: "book to audiobook",
        },
        {
          title: "AI Audiobook Generator",
          url: "https://echo3s.io/ai-audiobook-generator",
          keyword: "ai audiobook generator",
        },
        {
          title: "Convert Ebook to Audiobook",
          url: "https://echo3s.io/convert-ebook-to-audiobook",
          keyword: "ebook to audiobook",
        },
      ],
      audiobook_categories: [
        "Fiction",
        "Non-Fiction",
        "Self-Help",
        "Business",
        "Science",
        "Biography",
        "Technology",
        "History",
        "Philosophy",
        "Poetry",
      ],
    };
  • The tool 'get_social_links' is registered in the TOOL_DEFS array with its name, description, empty inputSchema, and a content function that returns the socialLinks data.
    {
      name: "get_social_links",
      description:
        "Get all Echo3s links — website, blog posts, landing pages, and contact information",
      inputSchema: { type: "object", properties: {}, required: [] },
      content: () => socialLinks,
    },
  • The stdio server iterates TOOL_DEFS and registers each tool (including get_social_links) via server.tool(), with the handler serializing the content() result to JSON.
    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),
          },
        ],
      }));
  • The Cloudflare Worker registers tools from TOOL_DEFS into a TOOLS record, wrapping each in a defToWorkerTool handler that stringifies the content() result.
    const TOOLS: Record<string, WorkerToolDef> = {};
    
    for (const def of TOOL_DEFS) {
      TOOLS[def.name] = defToWorkerTool(def);
    }
    TOOLS[CALCULATE_COST_DEF.name] = defToWorkerTool(CALCULATE_COST_DEF);
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only operation ('get') and lists what data is returned, but does not explicitly state read-only nature or any side effects. For a simple tool, this is adequate.

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?

Single sentence, front-loaded with the action, no redundant information. Every part is essential and clear.

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?

Given no parameters and no output schema, the description fully explains what the tool returns. It lists all expected link types, making it complete for the tool's complexity.

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?

No parameters exist in the schema, so schema coverage is 100%. The description adds value by enumerating the categories of links returned (website, blog posts, landing pages, contact information), providing meaning beyond the empty schema.

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 the tool's function: 'Get all Echo3s links' and lists specific link types (website, blog posts, landing pages, contact information). This distinguishes 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 Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives, but the purpose is straightforward and the tool has no parameters, making usage self-evident. Implicit usage is clear from the description.

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