Skip to main content
Glama
0xGval
by 0xGval

twitterSearchHelp

Search Twitter for Ethereum-related discussions to find community insights, technical support, and project updates for blockchain analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNogeneral

Implementation Reference

  • The handler function for the 'twitterSearchHelp' tool. It takes an optional 'topic' parameter and returns formatted Markdown text explaining Twitter search syntax for general, user-related, or date-related queries.
        async ({ topic }) => {
          // Simplified guide content from our resource
          const helpContent = {
            general: `# Twitter Search Syntax Guide
    
    Basic operators:
    - Simple keyword: \`ethereum\` - Finds tweets containing this word
    - Exact phrase: \`"ethereum scaling"\` - Finds the exact phrase
    - OR operator: \`ethereum OR solana\` - Finds tweets with either term
    - Exclusion: \`ethereum -solana\` - Finds tweets with ethereum but not solana
    
    Account filters:
    - From user: \`(from:username)\` - Tweets sent by a specific account
    - To user: \`(to:username)\` - Replies to a specific account
    - Mentioning: \`(@username)\` - Tweets that mention this account
    
    Other filters:
    - Date range: \`since:2024-01-01 until:2024-01-31\`
    - Media: \`has:links\`, \`has:images\`, \`has:videos\`
    - Engagement: \`min_faves:100\`, \`min_retweets:50\`, \`min_replies:10\``,
    
            user: `# User-Related Twitter Search Syntax
    
    - From specific user: \`(from:username)\` - Tweets sent by a specific account
    - To specific user: \`(to:username)\` - Replies to a specific account
    - Mentioning user: \`(@username)\` - Tweets that mention this account
    
    Examples:
    - \`(from:vitalikbuterin) ethereum\` - Tweets from Vitalik about Ethereum
    - \`(to:ethereum) help\` - Help requests sent to the Ethereum account`,
    
            date: `# Date-Related Twitter Search Syntax
    
    - Since date: \`since:YYYY-MM-DD\` - Tweets after this date
    - Until date: \`until:YYYY-MM-DD\` - Tweets before this date
    
    Example:
    - \`ethereum since:2024-01-01 until:2024-01-31\` - Ethereum tweets from January 2024`
          };
    
          // Return the requested help topic or general help
          return {
            content: [{
              type: "text",
              text: helpContent[topic] || helpContent.general
            }]
          };
        }
  • Zod schema defining the input parameters for the tool: an optional 'topic' string defaulting to 'general'.
    { 
      topic: z.string().optional().default("general")
    },
  • The complete registration of the 'twitterSearchHelp' tool using server.tool(), including schema and inline handler function.
      // Add a Twitter syntax help tool
      server.tool("twitterSearchHelp",
        { 
          topic: z.string().optional().default("general")
        },
        async ({ topic }) => {
          // Simplified guide content from our resource
          const helpContent = {
            general: `# Twitter Search Syntax Guide
    
    Basic operators:
    - Simple keyword: \`ethereum\` - Finds tweets containing this word
    - Exact phrase: \`"ethereum scaling"\` - Finds the exact phrase
    - OR operator: \`ethereum OR solana\` - Finds tweets with either term
    - Exclusion: \`ethereum -solana\` - Finds tweets with ethereum but not solana
    
    Account filters:
    - From user: \`(from:username)\` - Tweets sent by a specific account
    - To user: \`(to:username)\` - Replies to a specific account
    - Mentioning: \`(@username)\` - Tweets that mention this account
    
    Other filters:
    - Date range: \`since:2024-01-01 until:2024-01-31\`
    - Media: \`has:links\`, \`has:images\`, \`has:videos\`
    - Engagement: \`min_faves:100\`, \`min_retweets:50\`, \`min_replies:10\``,
    
            user: `# User-Related Twitter Search Syntax
    
    - From specific user: \`(from:username)\` - Tweets sent by a specific account
    - To specific user: \`(to:username)\` - Replies to a specific account
    - Mentioning user: \`(@username)\` - Tweets that mention this account
    
    Examples:
    - \`(from:vitalikbuterin) ethereum\` - Tweets from Vitalik about Ethereum
    - \`(to:ethereum) help\` - Help requests sent to the Ethereum account`,
    
            date: `# Date-Related Twitter Search Syntax
    
    - Since date: \`since:YYYY-MM-DD\` - Tweets after this date
    - Until date: \`until:YYYY-MM-DD\` - Tweets before this date
    
    Example:
    - \`ethereum since:2024-01-01 until:2024-01-31\` - Ethereum tweets from January 2024`
          };
    
          // Return the requested help topic or general help
          return {
            content: [{
              type: "text",
              text: helpContent[topic] || helpContent.general
            }]
          };
        }
      );
  • main.js:65-65 (registration)
    Top-level registration call to registerTwitterTools(server), which internally registers the 'twitterSearchHelp' tool among others.
    registerTwitterTools(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

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/0xGval/evm-mcp-tools'

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