Skip to main content
Glama
Beyond-Network-AI

Beyond MCP Server

get-thread

Extract threads or conversations from social platforms (Farcaster, Twitter, Telegram) using a specific thread ID to access and analyze structured data for LLM workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesSocial platform (farcaster, twitter, telegram)
threadIdYesThread or conversation ID

Implementation Reference

  • Registration and handler implementation of the 'get-thread' tool. Defines input schema (platform, threadId), fetches the thread via the platform-specific provider, formats it, and returns as text content. Handles provider not found and errors.
    server.tool(
      "get-thread",
      {
        platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
        threadId: z.string().describe("Thread or conversation ID")
      },
      async ({ platform, threadId }) => {
        try {
          const provider = providerRegistry.getProviderForPlatform(platform);
          
          if (!provider) {
            return {
              content: [{ type: "text", text: `Provider for platform '${platform}' not found or not enabled` }],
              isError: true
            };
          }
          
          const thread = await provider.getThread(threadId);
          
          return {
            content: [{ 
              type: "text", 
              text: formatThread(thread) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: `Error fetching ${platform} thread '${threadId}': ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Helper function to format the retrieved thread data (root post and replies) into a structured, readable text string for the tool response.
    function formatThread(thread: any): string {
      const rootContent = thread.content;
      const replies = thread.replies;
      
      const root = `
    Original Post by @${rootContent.authorUsername} (${rootContent.authorName}):
    "${rootContent.text}"
    - Posted: ${new Date(rootContent.createdAt).toLocaleString()}
    - Engagement: ${rootContent.likes || 0} likes, ${rootContent.reposts || 0} reposts, ${rootContent.replies || 0} replies
    - ID: ${rootContent.id}
    `;
      
      let repliesText = '';
      if (replies.length > 0) {
        repliesText = '\nReplies:\n\n' + replies.map((reply: SocialContent, index: number) => {
          return `[${index + 1}] @${reply.authorUsername} (${reply.authorName}): ${reply.text}
          - Posted: ${new Date(reply.createdAt).toLocaleString()}
          - Engagement: ${reply.likes || 0} likes, ${reply.reposts || 0} reposts, ${reply.replies || 0} replies
          - ID: ${reply.id}`;
        }).join('\n\n');
      } else {
        repliesText = '\nNo replies to this post.';
      }
      
      return `Thread on ${thread.platform}:\n${root}${repliesText}`;
    }
  • Calls registerContentTools which registers the 'get-thread' tool among others on the MCP server.
    registerContentTools(server, providerRegistry);
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no 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

Related 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/Beyond-Network-AI/beyond-mcp-server'

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