Skip to main content
Glama
Sign In
X-MCP

X-MCP

by mhqamx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

x_search_tweets

Search tweets by keyword with advanced syntax like 'from:user' or 'min_faves:1000'. Retrieve up to 50 results per query.

Instructions

按关键词搜索推文，支持 X 高级搜索语法

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "x_search_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo结果数量，默认20
queryYes搜索关键词，支持高级语法如 "from:example_user keyword"、"min_faves:1000" 等

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It only states search capability without mentioning side effects, authentication needs, rate limits, or whether results are read-only. This is insufficient for safe invocation.

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

Conciseness5/5

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

The description is a single sentence that immediately conveys the tool's purpose, with no wasted words. It is optimally concise and front-loaded.

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

Completeness3/5

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

Given no output schema, the description should explain return values (e.g., format, pagination). It does not, making it incomplete for an agent to fully understand the tool's behavior, though schema coverage compensates partially.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with both parameters described. The description adds little beyond the schema, which already provides examples and defaults. Baseline score of 3 is appropriate.

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 action (search) and resource (tweets), and mentions support for advanced search syntax. However, it does not explicitly distinguish from the sibling tool x_get_tweets, which may serve a similar purpose.

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?

No guidance on when to use this tool versus alternatives. The description lacks when-not-to-use scenarios or prerequisites, leaving the agent without contextual decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools