Skip to main content
Glama

get_social_sentiment_endpoints

Retrieve endpoints for social media analytics, sentiment analysis, influencer tracking, and trend detection across crypto, stocks, and NFTs. Analyze engagement metrics, track virality, and monitor real-time social sentiment with comprehensive indicators.

Instructions

Get all endpoints in the "Social Media & Sentiment Analytics" category. Endpoints for social media analytics, sentiment analysis, influencer tracking, social engagement metrics, trending topics analysis, news aggregation, creator analytics, post engagement tracking, social dominance metrics, Galaxy Score™, AltRank™, and comprehensive social sentiment indicators across crypto assets, stocks, and NFTs. Includes real-time social monitoring, influencer identification, content virality analysis, and social trend detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'get_social_sentiment_endpoints' tool (and other category tools). It fetches the list of tools in the 'Social Media & Sentiment Analytics' category using getAllToolsInCategory and formats them into a response using asTextContentResult.
      handler: async (
        args: Record<string, unknown> | undefined,
      ): Promise<any> => {
        const toolsInCategory = getAllToolsInCategory(category.category);
        
        return asTextContentResult({
          category: category.category,
          description: category.description,
          tools: toolsInCategory.map((tool ) => ({
            name: tool.name,
            description: tool.description
          })),
        });
      },
    };
  • Registration code that dynamically creates the 'get_social_sentiment_endpoints' tool object from the ToolRegistry, including name, description, schema, and handler.
    // Create category-specific endpoints that act as list functionality
    const categoryTools = ToolRegistry.map(category => {
      const categorySchema = z.object({});
      
      const categoryEndpointName = category.name;
      
      return {
        metadata: {
          resource: 'dynamic_tools',
          operation: 'read' as const,
          tags: ['category'],
        },
        tool: {
          name: categoryEndpointName,
          description: `Get all endpoints in the "${category.category}" category. ${category.description}`,
          inputSchema: zodToInputSchema(categorySchema),
        },
        handler: async (
          args: Record<string, unknown> | undefined,
        ): Promise<any> => {
          const toolsInCategory = getAllToolsInCategory(category.category);
          
          return asTextContentResult({
            category: category.category,
            description: category.description,
            tools: toolsInCategory.map((tool ) => ({
              name: tool.name,
              description: tool.description
            })),
          });
        },
      };
    });
    
    return [getEndpointTool, callEndpointTool, ...categoryTools];
  • ToolRegistry entry that defines the category name 'get_social_sentiment_endpoints', its description, and the list of underlying tools it exposes.
    {
      "category": "Social Media & Sentiment Analytics",
      "name": "get_social_sentiment_endpoints",
      "description": "Endpoints for social media analytics, sentiment analysis, influencer tracking, social engagement metrics, trending topics analysis, news aggregation, creator analytics, post engagement tracking, social dominance metrics, Galaxy Score™, AltRank™, and comprehensive social sentiment indicators across crypto assets, stocks, and NFTs. Includes real-time social monitoring, influencer identification, content virality analysis, and social trend detection.",
      "tools": [
        "discover_topic_influencers",
        "fetch_topic_news_articles",
        "analyze_topic_social_posts",
        "retrieve_topic_metrics",
        "list_trending_topics",
        "analyze_category_overview",
        "discover_category_topics",
        "fetch_category_social_content",
        "retrieve_category_news_feed",
        "list_category_influencers",
        "browse_trending_categories",
        "rank_social_influencers",
        "fetch_creator_profile",
        "track_creator_performance",
        "analyze_creator_content",
        "retrieve_post_analytics",
        "monitor_post_engagement"
      ]
    }
  • Helper function called by the handler to resolve the list of supported tools matching the names in the category's 'tools' array from supportedTools.
    export function getAllToolsInCategory(category: string){
      let categoryUsed = ToolRegistry.find(tool => tool.category === category);
      if(!categoryUsed){
        return []
      }
      const allWrappedTools = supportedTools
      // return all the tools from wrapped tools that are in the category (name match)
      let toolsInCategory = [];
      for (const tool of categoryUsed.tools){
        const wrappedTool = allWrappedTools.find(wrappedTool => wrappedTool.name === tool);
        if(wrappedTool){
          toolsInCategory.push(wrappedTool);
        }
        else console.log(`Tool ${tool} not found in wrapped tools`);
      }
      return toolsInCategory;
    }
  • Helper function used by the handler to format the result as MCP-compatible text content, with truncation for large responses.
    export function asTextContentResult(result: Object): any {
      // return {data: result}
      // Estimate token count (roughly 4 chars per token)
      const MAX_TOKENS = 25000;
      const CHARS_PER_TOKEN = 4;
      const maxChar = MAX_TOKENS * CHARS_PER_TOKEN; // ~100,000 chars for 25k tokens
      
      const jsonString = JSON.stringify(result, null, 2);
      
      if (jsonString.length > maxChar) {
        // Try to intelligently truncate if it's an array
        if (Array.isArray(result)) {
          const truncatedArray = result.slice(0, Math.floor(result.length * maxChar / jsonString.length));
          const truncatedJson = JSON.stringify({
            results: truncatedArray,
            truncated: true,
            originalLength: result.length,
            returnedLength: truncatedArray.length,
            message: "Response truncated due to size limits. Consider using pagination."
          }, null, 2);
          
          return {
            content: [
              {
                type: 'text',
                text: truncatedJson,
              },
            ],
          };
        }
        
        // For objects with results array
        if (typeof result === 'object' && result !== null && 'results' in result && Array.isArray((result as any).results)) {
          const originalResults = (result as any).results;
          const estimatedItemSize = jsonString.length / originalResults.length;
          const maxItems = Math.floor(maxChar / estimatedItemSize);
          
          const truncatedResult = {
            ...result,
            results: originalResults.slice(0, maxItems),
            truncated: true,
            originalCount: originalResults.length,
            returnedCount: maxItems,
            message: "Response truncated due to size limits. Use pagination parameters (limit/offset) for more results."
          };
          
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(truncatedResult, null, 2),
              },
            ],
          };
        }
        
        // Fallback to simple truncation
        const truncated = jsonString.substring(0, maxChar) + '\n... [TRUNCATED DUE TO SIZE LIMITS]';
        return {
          content: [
            {
              type: 'text',
              text: truncated,
            },
          ],
        };
      }
      
      return {
        content: [
          {
            type: 'text',
            text: jsonString,
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what endpoints are included (e.g., social media analytics, sentiment analysis) but does not mention critical behaviors such as whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness3/5

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

The description is front-loaded with the core purpose in the first sentence, but it becomes verbose with a long list of examples (e.g., 'Galaxy Score™, AltRank™') that could be condensed. While informative, some sentences do not earn their place by adding critical value beyond the initial scope, reducing efficiency.

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

Completeness2/5

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

Given the complexity (a tool retrieving endpoints with no output schema and no annotations), the description is incomplete. It details the category content but fails to explain the return format, pagination, error handling, or other behavioral aspects. Without annotations or an output schema, the description should provide more context to be fully helpful.

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?

The input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description does not add parameter information, which is unnecessary here. Since there are no parameters, the baseline score is 4, as the description does not need to compensate for any schema gaps.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get all endpoints in the "Social Media & Sentiment Analytics" category.' It specifies the resource (endpoints) and the category scope. However, it does not explicitly distinguish this tool from its siblings (e.g., get_defi_protocol_endpoints, get_market_and_price_endpoints), which all follow a similar 'get [category] endpoints' pattern, so it lacks sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lists the types of endpoints included but does not mention prerequisites, exclusions, or comparisons to other tools (e.g., when to use get_search_discovery_endpoints instead). This leaves the agent without explicit usage instructions.

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/hive-intel/hive-crypto-mcp'

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