x_api_send_chat_message
Post a chat message to a user through the X API. Use this tool when you need to send a direct message, with authentication scopes and tenant context applied.
Instructions
Send Chat Message. Use when: Send Chat Message. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: mutating, high-risk. Required permissions and prerequisites: OAuth 2 user token with scopes dm.write, tweet.read, users.read; OAuth 1a user token Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: id (path, unknown, required); body is used for the documented request payload. Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_upsert_principal_credentials, x_api_request. Safety warnings: This mutates X state. Validate scope, payload, and authorizationKey before use. Example: {"name":"x_api_send_chat_message","arguments":{"scopeTenantId":"default","scopeUserId":"default","id":"","body":{}}}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| body | No | ||
| scopeUserId | No | ||
| credentialKey | No | ||
| scopeTenantId | No | ||
| scopeAccountId | No | ||
| authorizationKey | No | ||
| preferredAuthType | No |