Do handle and date filters also restrict Grok thread fetches?

Definition: In xAI's X Search tool, allowed_x_handles, excluded_x_handles, from_date, and to_date apply to keyword and semantic searches. xAI documents thread fetches as a separate operation outside that handle and date filter scope.

Key facts

• xAI's X Search documentation lists keyword search, semantic search, user search, and thread fetch as operations available to Grok.
• allowed_x_handles limits posts considered to a supplied list of handles, while excluded_x_handles prevents posts from specified handles from being included in X Search tool invocations.
• The date window uses from_date and to_date: it starts at 00:00 UTC on the first date and ends immediately before the second date.
• xAI's scope statement assigns handle and date parameters to every keyword and semantic search, whatever query the model writes, and places thread fetches outside that scope.
• xAI's Tool Usage Details documentation names x_keyword_search, x_semantic_search, and x_thread_fetch as X Search functions.

Which operations receive the filters?

xAI describes X Search as a tool from which the model selects functions and decides how often to call them. A keyword search uses X's advanced search operators. A semantic search uses meaning rather than exact words. The same documentation describes a thread fetch as fetching one post with its parent posts and replies.

The filter scope is explicit: handle and date parameters apply to every keyword and semantic search, including searches whose query is written by the model. Thread fetches fall outside those parameters. A handle or date restriction configured on the enclosing x_search tool therefore has documented scope over the keyword and semantic branches, while the thread branch has its own fetch behavior.

What does the configuration look like?

The documented Responses API example combines a handle restriction with a date window:

tools=[{"type": "x_search", "allowed_x_handles": ["SpaceX"], "from_date": "2026-09-01", "to_date": "2026-10-01"}]

The parameter names are allowed_x_handles, excluded_x_handles, from_date, and to_date in the Responses API. Handle values are written without the @ sign. xAI treats allowed_x_handles and excluded_x_handles as mutually exclusive in one request. For a single day, xAI says to set to_date to the following day because the end date is excluded. The documented date format is YYYY-MM-DD for both fields.

What does a thread fetch contribute to usage?

The separate Tool Usage Details documentation places keyword search, semantic search, and thread fetch under the SERVER_SIDE_TOOL_X_SEARCH usage category. It says x_posts_fetched counts posts returned by those three functions, including parent and quoted posts and every post of a fetched thread. The count accumulates across X Search calls; a post returned by two searches counts twice.

The X Search page gives no separate handle or date option for filtering the parent posts or replies returned by x_thread_fetch. Its documented boundary is the operation level: the filters constrain keyword and semantic search, while thread fetches fall outside them.

Related terms

• Grok web search
• ChatGPT search
• Perplexity Sonar

FAQ

Can an allowed handle list limit a thread fetch?

No. xAI assigns handle parameters to keyword and semantic searches, placing thread fetches outside that documented scope.

Does a date window remove older posts from a fetched thread?

xAI documents the date window for search data and gives it a UTC start and exclusive end. The same documentation places thread fetches outside the date parameters, leaving no documented date filter inside a fetched thread.

Can allowed and excluded handles be combined?

The X Search parameter documentation treats allowed_x_handles and excluded_x_handles as mutually exclusive in the same request.

Sources

1. xAI, "X Search", 10 October 2026
2. xAI, "Tool Usage Details", 10 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer