X (Twitter) MCP integration for AI agents.
Connect AI agents to X (Twitter) through 71 structured actions, including add list member, add post to bookmarks, delete dm, and bookmarks by user. Review au…
- ACTION CONTRACTS
- 71
- AUTHENTICATION
- OAuth 2.0 + Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the X (Twitter) integration exposes
The X (Twitter) Agent App exposes 71 provider-backed actions for social and marketing work. Its current contract lets an authorized agent add a user account as a member of an x list, add a tweet to bookmarks for the authenticated user account, and delete a direct message event from the authenticated user account. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and Custom credentials. 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 X (Twitter) account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real X (Twitter) capabilities.
Showing 12 of 71 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_list_memberREADAdd a user account as a member of an X List.
add_post_to_bookmarksWRITEAdd a Tweet to bookmarks for the authenticated user account.
delete_dmHIGH IMPACTDelete a Direct Message event from the authenticated user account.
bookmarks_by_userREVIEWGet bookmarked Tweets for a user account.
create_compliance_jobWRITECreate a compliance job using app-only auth.
create_dm_conversationWRITECreate a new group Direct Message conversation with an initial message.
create_listREADCreate a new X List for the authenticated user account.
creation_of_a_postWRITECreate a Tweet for the authenticated X user.
delete_listHIGH IMPACTDelete a List owned by the authenticated user account.
follow_listREADFollow an X List from the authenticated user account.
follow_userREVIEWFollow a target user from the authenticated user account.
followers_by_user_idREVIEWGet followers for a user account.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add List Member
Add a user account as a member of an X List. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_list_memberControl Add Post To Bookmarks
Add a Tweet to bookmarks for the authenticated user account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_post_to_bookmarksVerify with Create List
Create a new X List for the authenticated user account. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_listSAFETY BOUNDARY
Operate X (Twitter) with explicit limits
- Authorize X (Twitter) with OAuth 2.0 and Custom credentials and grant only the provider access required by the selected actions.
- 20 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_dm`, `delete_list`, and `full_archive_search` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `twitter.list.read`, `twitter.list.write`, `twitter.users.read`, and `twitter.bookmark.write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the X (Twitter) task completed successfully.
CONNECTION MODEL
OAuth 2.0 + Custom credentials
X (Twitter) uses OAuth 2.0 and Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 42
- WRITE SIGNALS
- 13
- HIGH IMPACT
- 7
- REVIEW SIGNALS
- 9
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 X (Twitter).