search-boost-mcp

Overview Schema Source Related Servers Discussions Admin

X (Twitter) Search

x_search

Read-only

Search X/Twitter posts, accounts, and threads by keyword, user, or post ID to retrieve attributed content and diagnostics.

Instructions

Find X/Twitter posts, account material or available thread content. Credential-free retrieval is supported; configured authentication can improve coverage. Results include source attribution and diagnostics. Author/date filters require verifiable metadata; unverified candidates are omitted. Coverage may be incomplete, stale or empty. A post sample does not establish platform-wide sentiment, and a thread result need not contain the full conversation.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Mode: keyword (default) or semantic uses query; user uses username; thread uses post_id
`query`	No	Search terms and X filters (e.g. from:OpenAI), or a natural-language topic for semantic mode
`post_id`	No	Real X post ID or status URL for type=thread
`to_date`	No	Inclusive end date, YYYY-MM-DD (UTC)
`username`	No	X account handle for type=user
`from_date`	No	Inclusive start date, YYYY-MM-DD (UTC)
`max_results`	No	Requested result limit, 1–10
`allowed_x_handles`	No	Only these authors; mutually exclusive with excluded_x_handles
`excluded_x_handles`	No	Exclude these authors; mutually exclusive with allowed_x_handles

Output Schema

TableJSON Schema

Name	Required	Description	Default
`via`	Yes
`note`	No
`items`	Yes
`tookMs`	Yes
`results`	Yes
`cacheHit`	No
`inFlight`	No
`warnings`	No
`engineStats`	No
`enginesUsed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.4Oct 3, 2026

addedOutput schema / properties / engineStats

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "attempts": {
+        "type": "number"
+      },
+      "errors": {
+        "type": "number"
+      },
+      "note": {
+        "type": "string"
+      },
+      "successes": {
+        "type": "number"
+      },
+      "used": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "used",
+      "errors"
+    ],
+    "type": "object"
+  },
+  "type": "object"
+}

addedOutput schema / properties / enginesUsed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / inFlight
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed10 schema fields changedv0.2.2Sep 22, 2026

addedInput schema / properties / allowed_x_handles

Added value: +{
+  "description": "Only these authors; mutually exclusive with excluded_x_handles",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / excluded_x_handles

Added value: +{
+  "description": "Exclude these authors; mutually exclusive with allowed_x_handles",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

changedInput schema / properties / from_date / description

Previous value: -"YYYY-MM-DD"New value: +"Inclusive start date, YYYY-MM-DD (UTC)"

addedInput schema / properties / max_results / description
```
Added value: +"Requested result limit, 1–10"
```

addedInput schema / properties / post_id / description

Added value: +"Real X post ID or status URL for type=thread"

addedInput schema / properties / query / description

Added value: +"Search terms and X filters (e.g. from:OpenAI), or a natural-language topic for semantic mode"

changedInput schema / properties / to_date / description

Previous value: -"YYYY-MM-DD"New value: +"Inclusive end date, YYYY-MM-DD (UTC)"

addedInput schema / properties / type / description

Added value: +"Mode: keyword (default) or semantic uses query; user uses username; thread uses post_id"

addedInput schema / properties / username / description
```
Added value: +"X account handle for type=user"
```
addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

First observedv0.1.2Aug 17, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only cover readOnly/openWorld/no-destructive, and the description adds substantial context: credential-free vs authenticated coverage, that results include source attribution and diagnostics, that author/date filters require verifiable metadata and unverified candidates are dropped, and that coverage may be incomplete, stale or empty. It even warns that a sample does not establish platform-wide sentiment. This is exactly the kind of behavior disclosure annotations cannot supply.

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

Conciseness4/5

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

Six compact sentences, each carrying distinct information (capability, auth, output, filter constraint, coverage limits, interpretation caveat). Front-loaded with the core capability and free of filler, though the telegraphic style gives it a slightly dense, checklist feel.

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

Completeness4/5

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

With an output schema present, the description needn't explain return values, and it correctly focuses on credentials, filter constraints and coverage limitations. For a 9-parameter, open-world search tool it covers what an agent needs to call it responsibly, though it never clarifies the division of labor with the sibling search tools.

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?

Schema description coverage is 100%, so the parameter baseline is 3. The description earns above baseline by adding a behavioral constraint on the filter parameters: author/date filters require verifiable metadata and unverified candidates are omitted, which tells the agent those parameters may silently narrow results. It still doesn't add syntax or format detail beyond the schema.

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 states a specific verb and resource ('Find X/Twitter posts, account material or available thread content'), so an agent immediately knows the domain and operation. It does not, however, distinguish this tool from siblings like fused_search or search_layer, leaving the agent to infer the boundary. Clear but not differentiating.

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

Usage Guidelines3/5

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

Usage context is implied ('Credential-free retrieval is supported; configured authentication can improve coverage') and caveats are given for when filters work, but there is no explicit when-to-use guidance relative to the sibling search tools. The mode selection (keyword/semantic/user/thread) is left entirely to the schema. Adequate but with a clear gap in routing guidance.

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

Deploy Server