Skip to main content
Glama
Beyond-Network-AI

Beyond MCP Server

get-trending-topics

Retrieve trending topics from social platforms like Farcaster, Twitter, and Telegram to analyze popular conversations and trends. Specify platform and limit for tailored results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of trending topics to return
platformYesSocial platform (farcaster, twitter, telegram)

Implementation Reference

  • The handler function for the 'get-trending-topics' tool. It retrieves the appropriate provider for the platform, calls getTrendingTopics on it with the limit, formats the topics using formatTrendingTopics, and returns them as text content. Handles errors by returning an error message.
    async ({ platform, limit = 10 }) => {
      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 topics = await provider.getTrendingTopics({ limit });
        
        return {
          content: [{ 
            type: "text", 
            text: formatTrendingTopics(topics, platform) 
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: `Error fetching ${platform} trending topics: ${error instanceof Error ? error.message : String(error)}` 
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining the parameters for the get-trending-topics tool: required platform string and optional limit number.
    {
      platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
      limit: z.number().optional().describe("Maximum number of trending topics to return")
    },
  • The server.tool call that registers the 'get-trending-topics' tool with MCP server, providing the name, input schema, and handler function.
    server.tool(
      "get-trending-topics",
      {
        platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
        limit: z.number().optional().describe("Maximum number of trending topics to return")
      },
      async ({ platform, limit = 10 }) => {
        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 topics = await provider.getTrendingTopics({ limit });
          
          return {
            content: [{ 
              type: "text", 
              text: formatTrendingTopics(topics, platform) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: `Error fetching ${platform} trending topics: ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Helper function used by the handler to format the array of trending topics into a numbered list string for the response.
    function formatTrendingTopics(topics: string[], platform: string): string {
      if (topics.length === 0) {
        return `No trending topics available for ${platform}.`;
      }
      
      const formattedTopics = topics.map((topic, index) => {
        return `${index + 1}. ${topic}`;
      }).join('\n');
      
      return `Trending Topics on ${platform}:\n\n${formattedTopics}`;
    }
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