Skip to main content
Glama

Vee3

by io.github.Vee3io

x-twitter.search

Search public X (Twitter) posts matching a keyword or phrase.

Returns a timeline of matching posts with tweet text, engagement counts, author info, media, and quoted tweets. Use cursor from next_cursor to fetch the next page. search_type controls ranking: Top (default), Latest, Media, People, or Lists.

Cost = 5 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keywords or phrase.
cursorNoPagination cursor from a previous response next_cursor field.
search_typeNoResult ranking mode.Top

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoSearch status from the upstream provider (ok on success).
timelineNoMatching posts from the search. Additional provider-specific fields may appear on each entry.
next_cursorNoCursor for the next results page, when available.
prev_cursorNoCursor for the previous results page, when available.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changed
    • changedOutput schema / $defs / SearchXResponseTimelineItem / properties / display_text_range / anyOf
      Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/SearchXResponseTimelineItemDisplayTextRangeItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SearchXResponseTimelineItem / properties / display_text_range / description
      Previous value: -"Start and end indices for the display text range."New value: +"Start and end character indices for the display text range."
    • changedOutput schema / $defs / SearchXResponseTimelineItem / properties / media / anyOf
      Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/SearchXResponseTimelineItemMediaItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/SearchXResponseTimelineItemMedia"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SearchXResponseTimelineItem / properties / media / description
      Previous value: -"Attached media items when present."New value: +"Attached media grouped by type (for example video and photo arrays) when present."
    • removedOutput schema / $defs / SearchXResponseTimelineItem / properties / media / title
      Removed value: -"Media"
    • removedOutput schema / $defs / SearchXResponseTimelineItemDisplayTextRangeItem
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "index": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Character index in the tweet text.",
-      "title": "Index"
-    }
-  },
-  "title": "SearchXResponseTimelineItemDisplayTextRangeItem",
-  "type": "object"
-}
    • changedOutput schema / $defs / SearchXResponseTimelineItemEntitiesHashtagsItem / properties / indices / anyOf
      Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/SearchXResponseTimelineItemEntitiesHashtagsItemIndicesItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SearchXResponseTimelineItemEntitiesHashtagsItem / properties / indices / description
      Previous value: -"Start and end indices in the tweet text."New value: +"Start and end character indices in the tweet text."
    • removedOutput schema / $defs / SearchXResponseTimelineItemEntitiesHashtagsItemIndicesItem
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "index": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Character index in the tweet text.",
-      "title": "Index"
-    }
-  },
-  "title": "SearchXResponseTimelineItemEntitiesHashtagsItemIndicesItem",
-  "type": "object"
-}
    • changedOutput schema / $defs / SearchXResponseTimelineItemEntitiesUserMentionsItem / properties / indices / anyOf
      Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/SearchXResponseTimelineItemEntitiesUserMentionsItemIndicesItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SearchXResponseTimelineItemEntitiesUserMentionsItem / properties / indices / description
      Previous value: -"Start and end indices in the tweet text."New value: +"Start and end character indices in the tweet text."
    • removedOutput schema / $defs / SearchXResponseTimelineItemEntitiesUserMentionsItemIndicesItem
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "index": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Character index in the tweet text.",
-      "title": "Index"
-    }
-  },
-  "title": "SearchXResponseTimelineItemEntitiesUserMentionsItemIndicesItem",
-  "type": "object"
-}
    • addedOutput schema / $defs / SearchXResponseTimelineItemMedia
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "photo": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/SearchXResponseTimelineItemMediaPhotoItem"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Photo media items when present.",
+      "title": "Photo"
+    },
+    "video": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/SearchXResponseTimelineItemMediaVideoItem"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Video media items when present.",
+      "title": "Video"
+    }
+  },
+  "title": "SearchXResponseTimelineItemMedia",
+  "type": "object"
+}
    • removedOutput schema / $defs / SearchXResponseTimelineItemMediaItem
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "media_url_https": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "HTTPS URL for the media asset.",
-      "title": "Media Url Https"
-    },
-    "type": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Media type (for example photo or video).",
-      "title": "Type"
-    }
-  },
-  "title": "SearchXResponseTimelineItemMediaItem",
-  "type": "object"
-}
    • addedOutput schema / $defs / SearchXResponseTimelineItemMediaPhotoItem
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "media_url_https": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "HTTPS URL for the photo asset.",
+      "title": "Media Url Https"
+    }
+  },
+  "title": "SearchXResponseTimelineItemMediaPhotoItem",
+  "type": "object"
+}
    • addedOutput schema / $defs / SearchXResponseTimelineItemMediaVideoItem
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "media_url_https": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "HTTPS URL for the video thumbnail or asset.",
+      "title": "Media Url Https"
+    },
+    "variants": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/SearchXResponseTimelineItemMediaVideoItemVariantsItem"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Available video quality variants when present.",
+      "title": "Variants"
+    }
+  },
+  "title": "SearchXResponseTimelineItemMediaVideoItem",
+  "type": "object"
+}
    • addedOutput schema / $defs / SearchXResponseTimelineItemMediaVideoItemVariantsItem
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "bitrate": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Video bitrate when provided.",
+      "title": "Bitrate"
+    },
+    "content_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "MIME type for the media variant.",
+      "title": "Content Type"
+    },
+    "url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "HTTPS URL for the media variant.",
+      "title": "Url"
+    }
+  },
+  "title": "SearchXResponseTimelineItemMediaVideoItemVariantsItem",
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must convey behavior. It states the return content (tweet text, engagement counts, author info, media, quoted tweets), pagination behavior, search_type ranking, and cost in tokens. It implies a read-only search operation and discloses the cost, which is valuable behavioral context.

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 three concise sentences: purpose, result details, and cost. Every sentence provides useful information and is front-loaded. No fluff or redundant content.

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

Completeness5/5

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

For a simple search tool with an output schema, the description is complete: it covers the query, return fields, pagination, ranking modes, and cost. It doesn't need to detail return values because an output schema exists. No obvious gaps.

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%, so parameters are already well-documented. The description adds little beyond the schema: it restates cursor usage and search_type options in natural language, but doesn't introduce new semantics. Baseline 3 is appropriate given schema coverage.

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

Purpose5/5

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

The description clearly states 'Search public X (Twitter) posts matching a keyword or phrase.' The verb 'Search' plus the resource 'public X posts' gives a specific purpose. It also distinguishes itself from sibling tools like tweet_info or user_timeline by focusing on keyword search.

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

Usage Guidelines4/5

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

The description gives clear context on what the tool does and how to paginate via 'next_cursor', and explains search_type options. It does not explicitly mention when not to use it or name alternative tools, but the purpose is distinct enough to infer usage.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources