Tools / X (Twitter) / How to
social.search has no date field, but the query passes X's own search operators through. Add since:2026-10-01 until:2026-10-15 after the keyword and the posts come back from that window only, with text, author, date, likes, replies and views. Use it to read what people said during a launch or an event.
Ask your agent
Pull tweets about devday for each day from October 6 to 14 and chart the daily views.
Connect RouterGrowth once, then ask in plain words. New workspaces start with $1 of credit. Get a key or read the setup guide.
A real run
One call to social.search (social post search), run through RouterGrowth on October 26, 2026. These are the first rows it returned; fields that name a person are masked.
| text | author | posted | views |
|---|---|---|---|
| At DevDay, we introduced ChatGPT Space: a new home for your team to collaborate with AI to get work done. In Space, you can create living… | Ch*** | 2026-10-14 | 268112 |
| Has anyone else noticed that OpenAI seems to be going downhill since DevDay? | @zi*** | 2026-10-14 | 23970 |
| Enjoying the #DevDay Exchange Community event in Santiago de Chile #DevDayCommunity https://t.co/aqJqD62p7K | @Fe*** | 2026-10-14 | 398 |
Ten tweets for devday between October 1 and 15: every one inside the window, all from October 14, the last day before until.
Step by step
Keyword, then since:YYYY-MM-DD and until:YYYY-MM-DD. until is the day after the last one you want.
platform x, the query and a limit. Check created_at on the results.
Results run newest first, so a wide window fills up with its last day. Run one call per day to cover it evenly.
social.comments on a tweet URL returns the replies under it.
Price
List prices on X, read from the catalog when this page was built. The exact figure is quoted before every run, and a monthly plan lowers it.
In practice
You describe the job; the agent picks the calls, shows the price and runs them.
Pull tweets about devday for each day from October 6 to 14 and chart the daily views.
Find what people tweeted about our launch in the two days after it, then read the replies on the most viewed one.
Connect
One MCP server for Claude, ChatGPT, Claude Code, Codex and Cursor, or the same call over the CLI and REST with the input above.
claude mcp add --transport http routergrowth https://api.routergrowth.com/mcp
npm install -g routergrowth && routergrowth setup
routergrowth run -c social.search -i '{"platform": "x", "query": "devday since:2026-10-01 until:2026-10-15", "limit": 10}'curl -X POST https://api.routergrowth.com/v1/run \
-H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \
-d '{"capability": "social.search", "input": {"platform": "x", "query": "devday since:2026-10-01 until:2026-10-15", "limit": 10}}'Worth knowing
The dates work because X reads since: and until: inside the query. The capability has no date setting of its own.
All ten results here fell on October 14. Split the window by day for a full picture.
Read created_at on every post before you report a count for a window.
FAQ
No. until:2026-10-15 stops before October 15, so the last posts here are from October 14.
X reads from:handle in the query too, so it should narrow a window to one account; test it with a small limit first.
The search reaches older public tweets; test the window you need with a small limit first.
Each call is priced per post returned, so one call per day costs about the same as one call over a week with the same limit.
More on X (Twitter)
Reading this as an agent? This page as markdown: /tools/x-twitter/tweet-search-by-date.md
Connect your agent once. The first calls run on the $1 that comes with signup.