TwitterAPI.io MCP integration for AI agents.
Connect AI agents to TwitterAPI.io through 39 structured actions, including advanced search tweets, add monitored tweet user, and delete tweet filter rule. R…
- ACTION CONTRACTS
- 39
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TwitterAPI.io integration exposes
The TwitterAPI.io Agent App exposes 39 provider-backed actions for social and data work. Its current contract lets an authorized agent run an advanced twitter search query, add an x user to real-time tweet monitoring, and delete a webhook/websocket tweet filter rule. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TwitterAPI.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TwitterAPI.io capabilities.
Showing 12 of 39 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
advanced_search_tweetsREADRun an advanced Twitter search query.
INPUTS: query / queryType / cursor
add_monitored_tweet_userWRITEAdd an X user to real-time Tweet monitoring.
INPUTS: xUserName
delete_tweet_filter_ruleHIGH IMPACTDelete a Webhook/WebSocket tweet filter rule.
INPUTS: ruleId
add_tweet_filter_ruleWRITEAdd a Webhook/WebSocket tweet filter rule.
INPUTS: tag / value / intervalSeconds
batch_get_usersREADRetrieve multiple X user profiles by user ID.
INPUTS: userIds
check_follow_relationshipREADCheck whether one X user follows or is followed by another user.
INPUTS: sourceUserName / targetUserName
get_account_infoREADRetrieve twitterapi.io account credit information for the API key.
get_articleREADRetrieve an X article by Tweet ID.
INPUTS: tweetId
get_community_infoREADRetrieve information about an X Community.
INPUTS: communityId
get_community_membersREADRetrieve members of an X Community.
INPUTS: communityId / cursor
get_community_moderatorsREADRetrieve moderators of an X Community.
INPUTS: communityId / cursor
get_community_tweetsREADRetrieve Tweets from an X Community.
INPUTS: communityId / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
advanced_search_tweets
queryREQUIRED- The advanced search query.
queryTypeREQUIRED- The search result ordering.
cursorOPTIONAL- The pagination cursor. Use an empty string or omit it for the first page.
add_monitored_tweet_user
xUserNameOPTIONAL- The X screen name without the @ prefix.
delete_tweet_filter_rule
ruleIdOPTIONAL- The twitterapi.io tweet filter rule ID.
add_tweet_filter_rule
tagOPTIONAL- A custom tag that identifies the tweet filter rule.
valueOPTIONAL- The Twitter search rule used to filter Tweets.
intervalSecondsOPTIONAL- The interval, in seconds, used to check matching Tweets.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Advanced Search Tweets
Run an advanced Twitter search query. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
advanced_search_tweetsControl Add Monitored Tweet User
Add an X user to real-time Tweet monitoring. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_monitored_tweet_userVerify with Batch Get Users
Retrieve multiple X user profiles by user ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
batch_get_usersSAFETY BOUNDARY
Operate TwitterAPI.io with explicit limits
- Authorize TwitterAPI.io with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_tweet_filter_rule` and `remove_monitored_tweet_user` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in TwitterAPI.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the TwitterAPI.io task completed successfully.
CONNECTION MODEL
API key
TwitterAPI.io API key used with the X-API-Key request header. Create or copy it from your TwitterAPI.io dashboard: https://twitterapi.io/dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 34
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TwitterAPI.io.