Skip to content

X

Updated View as Markdown

Connect X and enable the operations your application needs. Each person authorizes their own account.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Read saved posts

Help me with this task in X: Read saved posts. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: x-library.bookmarks.list

Read liked posts

Help me with this task in X: Read liked posts. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: x-library.likes.list

What you can do (5)

What you can do

Available commands: 5 (5 read, 0 write). Enable only the commands your application needs.

Command Effect
Read saved posts — x-library.bookmarks.list Read
Read liked posts — x-library.likes.list Read
Read bookmark folders — x-library.folders.list Read
Read posts in a bookmark folder — x-library.folders.posts.list Read
Search recent posts (one page) — x-api.search-recent Read

Connect and use

Connect and use

Tooluse.net supplies the provider credentials for these commands. You do not need to apply for a provider API key. Select Tooluse.net credentials in the connection form; complete provider sign-in or authorization if prompted.

Connect this integration, select Tooluse.net credentials, choose the commands you need and save. Complete provider sign-in if prompted.

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "maxResults": 20
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Read saved posts — x-library.bookmarks.list

Run Read saved posts with X. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
maxResults integer Optional minimum: 1; maximum: 100
nextToken string Optional maxLength: 2048; pattern: "^[A-Za-z0-9_-]{1,2048}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "maxResults": 20
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Read liked posts — x-library.likes.list

Run Read liked posts with X. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
maxResults integer Optional minimum: 1; maximum: 100
nextToken string Optional maxLength: 2048; pattern: "^[A-Za-z0-9_-]{1,2048}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "maxResults": 20
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Read bookmark folders — x-library.folders.list

Run Read bookmark folders with X. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
maxResults integer Optional minimum: 1; maximum: 100
nextToken string Optional maxLength: 2048; pattern: "^[A-Za-z0-9_-]{1,2048}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "maxResults": 20
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Read posts in a bookmark folder — x-library.folders.posts.list

Run Read posts in a bookmark folder with X. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
maxResults integer Optional minimum: 1; maximum: 100
nextToken string Optional maxLength: 2048; pattern: "^[A-Za-z0-9_-]{1,2048}$"
folderId string Required pattern: "^[0-9]{1,19}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "maxResults": 20,
  "folderId": "123456789"
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Search recent posts (one page) — x-api.search-recent

Run Search recent posts (one page) with X. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query string Required minLength: 1; maxLength: 512
startTime string Required format: "date-time"
endTime string Required format: "date-time"
maxResults integer Optional minimum: 10; maximum: 100
sortOrder string Optional enum: ["recency","relevancy"]
nextToken string Optional minLength: 1; maxLength: 2048; pattern: "^[A-Za-z0-9_-]+$"

Full JSON Schema

Full JSON Schema

Example input

{
  "query": "Ubuntu regression -is:retweet",
  "startTime": "2026-11-02T02:00:00Z",
  "endTime": "2026-11-03T02:00:00Z",
  "maxResults": 100,
  "sortOrder": "relevancy"
}

At most 2 provider requests per invocation; timeout: 60 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close