X community posts
Get posts from an X community by ID, with sorting and pagination.
Start with your agent
Download and install the dedicated Mouter Skill for “X community posts”: https://mouter.ai/skills/twitter_community_timeline.zip
Pricing
0.01 credits per call
Each additional page is billed as a separate call.
Usage example
Agent
Example input
Use twitter_community_timeline. Look up X community posts using community_id 123456789 and summarize community or channel details, content and pagination. Confirm inputs and estimated cost before running.
Example output
Example only: X community posts has not been run. Once a task succeeds, its result contains these fields:
- platformtext
- itemslist: audio_tracks, music, topics, id, url
- paginationobject: has_more, next_cursor, total
- retrieved_atnumber
- community_idtext
Values depend on your input. The matching JSON example structure is in the API tab.
Continue this example
For the first batch, omit cursor. When pagination.has_more indicates more results and pagination.next_cursor is present, pass the returned pagination.next_cursor as cursor in the next call. Keep the original identifiers, filters and ordering unchanged. Each request retrieves one batch. Illustrative requests and response fragment; no calls are executed.
1. Initial request
{
"name": "twitter_community_timeline",
"arguments": {
"community_id": "123456789"
}
}2. Returned continuation
{
"pagination": {
"next_cursor": "<NEXT_CURSOR>",
"has_more": true
}
}3. Follow-up request
{
"name": "twitter_community_timeline",
"arguments": {
"community_id": "123456789",
"cursor": "<NEXT_CURSOR>"
}
}- Getting started: provide community ID. Adjust sort order, continuation cursor as needed.
FAQ
Which community_id should I pass to X community posts?
X community posts: Getting started: provide community ID. Adjust sort order, continuation cursor as needed. community_id: 1–128 characters; format ^[0-9]+$ Illustrative values on this page: community_id="123456789". Replace example identifiers and URLs with your target before running.
Which result details can I use from X community posts?
Get posts from an X community by ID, with sorting and pagination. The result includes items, pagination, community_id. Read result.items[]: id, url, title, text, content_html, author, published_at, published_at_text, cover_url, media. result.retrieved_at records retrieval time; content publication times are separate source fields. Optional fields depend on what the source returns; retain null or missing values when combining results.
How can I sort or narrow results from X community posts?
X community posts: order: values relevance / recent; default "relevance".
How do I retrieve more results from X community posts?
X community posts: For the first batch, omit cursor. When pagination.has_more indicates more results and pagination.next_cursor is present, pass the returned pagination.next_cursor as cursor in the next call. Keep the original identifiers, filters and ordering unchanged. Each request retrieves one batch.
How is X community posts billed for each request?
Published reference rates: Standard rate: 0.01 credits · Per call. Each additional page is billed as a separate call. Final charges use your account’s rates and actual usage.