Skip to main content
Glama
Beyond-Network-AI

Beyond MCP Server

get-trending-feed

Retrieve trending content from social platforms like Farcaster, Twitter, and Telegram. Specify time windows, providers, and item limits to analyze and monitor popular posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of trending items to return (default: 20)
platformYesSocial platform (farcaster, twitter, telegram)
providerNoProvider to use for trending feed (default: neynar)
timeWindowNoTime window for trending content (default: 24h)

Implementation Reference

  • Registration of the 'get-trending-feed' tool on the MCP server, including input schema (Zod validation) and the inline handler function that executes the tool logic by delegating to the platform provider's getTrendingFeed method and formatting the response.
    // Get trending feed tool
    server.tool(
      "get-trending-feed",
      {
        platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
        provider: z.enum(['neynar', 'openrank', 'mbd']).optional().describe("Provider to use for trending feed (default: neynar)"),
        timeWindow: z.enum(['1h', '6h', '12h', '24h', '7d', '30d']).optional().describe("Time window for trending content (default: 24h)"),
        limit: z.number().optional().describe("Maximum number of trending items to return (default: 20)")
      },
      async ({ platform, provider, timeWindow, limit = 20 }) => {
        try {
          // Check if platform supports trending feed
          if (platform !== 'farcaster') {
            return {
              content: [{ 
                type: "text", 
                text: `Trending feed with multiple providers is currently only supported for Farcaster. For ${platform}, please use the get-trending-topics tool instead.` 
              }],
              isError: true
            };
          }
    
          const providerInstance = providerRegistry.getProviderForPlatform(platform);
          
          if (!providerInstance) {
            return {
              content: [{ type: "text", text: `Provider for platform '${platform}' not found or not enabled` }],
              isError: true
            };
          }
          
          const feed = await providerInstance.getTrendingFeed({ provider, timeWindow, limit });
          
          return {
            content: [{ 
              type: "text", 
              text: formatTrendingFeed(feed, platform) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: `Error fetching ${platform} trending feed: ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Supporting utility function that formats the array of SocialContent from the trending feed into a human-readable markdown-style text response for the tool output.
    function formatTrendingFeed(feed: SocialContent[], platform: string): string {
      if (feed.length === 0) {
        return `No trending content available for ${platform}.`;
      }
      
      const formattedFeed = feed.map((item, index) => {
        return `[${index + 1}] @${item.authorUsername} (${item.authorName}): "${item.text}"
        - Posted: ${new Date(item.createdAt).toLocaleString()}
        - Engagement: ${item.likes || 0} likes, ${item.reposts || 0} reposts, ${item.replies || 0} replies
        - ID: ${item.id}`;
      }).join('\n\n');
      
      return `Trending Feed on ${platform}:\n\n${formattedFeed}`;
    }
  • Top-level registration call to registerContentTools, which in turn registers the 'get-trending-feed' tool (and other content tools) on the MCP server instance.
    // Register MCP capabilities
    registerContentResources(server, providerRegistry);
    registerContentTools(server, providerRegistry);
    registerContentPrompts(server);
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