Skip to main content
Glama
Beyond-Network-AI

Beyond MCP Server

search-content

Search content across social platforms (Farcaster, Twitter, Telegram) using a query and retrieve relevant results. Specify the platform and limit responses for focused data extraction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
platformYesSocial platform (farcaster, twitter, telegram)
queryYesSearch query

Implementation Reference

  • Handler function that executes the 'search-content' tool logic: logs the call, retrieves the platform provider from registry, checks availability, calls provider.searchContent, formats results with formatSearchResults, and returns formatted text or error.
    async ({ platform, query, limit = 10 }) => {
      try {
        console.error(`search-content tool called for platform: ${platform}, query: ${query}`);
        const provider = providerRegistry.getProviderForPlatform(platform);
        
        if (!provider) {
          console.error(`Provider for platform '${platform}' not found or not enabled`);
          return {
            content: [{ type: "text", text: `Provider for platform '${platform}' not found or not enabled` }],
            isError: true
          };
        }
        
        // Check if the provider is available
        console.error(`Checking if provider ${provider.name} is available`);
        const isAvailable = await provider.isAvailable();
        if (!isAvailable) {
          console.error(`Provider ${provider.name} is not available`);
          return {
            content: [{ type: "text", text: `Provider for platform '${platform}' is not available` }],
            isError: true
          };
        }
        
        console.error(`Using provider: ${provider.name} for search`);
        const results = await provider.searchContent(query, { limit });
        console.error(`Search results count: ${results.length}`);
        
        return {
          content: [{ 
            type: "text", 
            text: formatSearchResults(results, query, platform) 
          }]
        };
      } catch (error) {
        console.error(`Error in search-content tool:`, error);
        return {
          content: [{ 
            type: "text", 
            text: `Error searching ${platform} for '${query}': ${error instanceof Error ? error.message : String(error)}` 
          }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'search-content' tool defining parameters: platform (string), query (string), limit (optional number).
      platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
      query: z.string().describe("Search query"),
      limit: z.number().optional().describe("Maximum number of results to return")
    },
  • Registers the 'search-content' tool on the MCP server with its name, input schema, and handler function.
      "search-content",
      {
        platform: z.string().describe("Social platform (farcaster, twitter, telegram)"),
        query: z.string().describe("Search query"),
        limit: z.number().optional().describe("Maximum number of results to return")
      },
      async ({ platform, query, limit = 10 }) => {
        try {
          console.error(`search-content tool called for platform: ${platform}, query: ${query}`);
          const provider = providerRegistry.getProviderForPlatform(platform);
          
          if (!provider) {
            console.error(`Provider for platform '${platform}' not found or not enabled`);
            return {
              content: [{ type: "text", text: `Provider for platform '${platform}' not found or not enabled` }],
              isError: true
            };
          }
          
          // Check if the provider is available
          console.error(`Checking if provider ${provider.name} is available`);
          const isAvailable = await provider.isAvailable();
          if (!isAvailable) {
            console.error(`Provider ${provider.name} is not available`);
            return {
              content: [{ type: "text", text: `Provider for platform '${platform}' is not available` }],
              isError: true
            };
          }
          
          console.error(`Using provider: ${provider.name} for search`);
          const results = await provider.searchContent(query, { limit });
          console.error(`Search results count: ${results.length}`);
          
          return {
            content: [{ 
              type: "text", 
              text: formatSearchResults(results, query, platform) 
            }]
          };
        } catch (error) {
          console.error(`Error in search-content tool:`, error);
          return {
            content: [{ 
              type: "text", 
              text: `Error searching ${platform} for '${query}': ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Helper function used by the handler to format the search results into a readable text string for the LLM.
    function formatSearchResults(results: SocialContent[], query: string, platform: string): string {
      if (results.length === 0) {
        return `No results found for query: "${query}" on ${platform}`;
      }
      
      const formattedResults = results.map((result, index) => {
        return `[${index + 1}] @${result.authorUsername} (${result.authorName}): ${result.text}
        - Posted: ${new Date(result.createdAt).toLocaleString()}
        - Engagement: ${result.likes || 0} likes, ${result.reposts || 0} reposts, ${result.replies || 0} replies
        - ID: ${result.id}`;
      }).join('\n\n');
      
      return `Search Results for "${query}" on ${platform}:\n\n${formattedResults}`;
    }
  • Top-level call to registerContentTools during MCP server setup, which includes registration of the 'search-content' tool.
    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