Skip to main content
Glama
Xquik-dev

X Twitter Scraper

xquik

Destructive

:

Instructions

Execute authenticated X (Twitter) API calls to read data, publish content, and manage accounts across 121 REST endpoints.

When to use

  • Use after calling 'explore' to discover the endpoint path and parameters.

  • Use for any live X/Twitter operation: search tweets, look up users, post tweets, like, retweet, follow, send DMs, run giveaway draws, monitor accounts, extract bulk data, compose tweets, and more.

When NOT to use

  • Do NOT use to discover endpoints — use 'explore' first.

  • Do NOT pass API keys or auth headers — authentication is injected automatically.

Behavior

  • Executes the provided async function in a sandboxed environment with xquik.request(path, options?) and spec.endpoints available.

  • Sandboxed via Node.js VM: no filesystem, no global network access — only xquik.request() is available. Console calls are silently ignored.

  • Execution timeout: 60 seconds per invocation, 60 seconds per individual API request.

  • Read operations (GET) return JSON objects with the requested data. Write operations (POST/DELETE) return { success: true } or { success: true, warning: '...' }.

  • Pagination: responses include has_next_page (boolean) and next_cursor (string). Pass cursor as a query param for the next page.

  • Can be destructive: write operations (POST/DELETE) modify data on X (tweets, follows, DMs, profile).

Error handling

  • 402: Subscription required or insufficient credits. Call POST /api/v1/subscribe to get a checkout URL.

  • 429: Rate limited. Retry after backoff.

  • 404: Resource not found (user, tweet, or monitor does not exist).

  • 200 with warning field: Probable success — do NOT retry.

Costs

  • Free: compose, styles, drafts, radar, subscribe, account, api-keys, support.

  • 1 credit/read ($0.00015): tweet search, timeline, bookmarks, favoriters.

  • 10 credits/write ($0.0015): tweet, like, retweet, follow, DM.

Input format

Write an async arrow function using xquik.request(path, { method?, body?, query? }). Auth is automatic.

Examples

Search tweets: async () => xquik.request('/api/v1/x/tweets/search', { query: { q: 'AI agents', limit: '50' } }) Get user: async () => xquik.request('/api/v1/x/users/elonmusk') Post tweet: async () => { const { accounts } = await xquik.request('/api/v1/x/accounts'); return xquik.request('/api/v1/x/tweets', { method: 'POST', body: { account: accounts[0].xUsername, text: 'Hello!' } }); }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript async arrow function that calls xquik.request(path, options?) to execute X/Twitter API operations. Auth is injected automatically. Example: async () => xquik.request('/api/v1/x/tweets/search', { query: { q: 'AI', limit: '20' } })
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare destructive/open-world status; the description substantially expands with sandboxing constraints (Node.js VM, no filesystem), execution timeouts (60s), pagination mechanics (has_next_page, next_cursor), return value schemas (JSON objects vs success objects), credit costs ($0.00015/read, $0.0015/write), and specific error code meanings (402, 429, 404). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Length is substantial but justified by tool complexity (sandboxed code execution, 121 endpoints, credit system). Information is front-loaded (purpose in first sentence) and hierarchically organized with clear headers (When to use, Behavior, Costs, Examples). Every section provides distinct operational value; examples are concise and illustrative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description comprehensively covers: return value structures (in Behavior), pagination (critical for 121 endpoints), error handling, financial costs (credit system), sibling relationships, and execution constraints. No gaps remain for agent invocation decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a detailed description for the single 'code' parameter. The description adds significant semantic value through the 'Input format' section and three concrete examples showing async arrow function patterns, method chaining, and query structures that clarify how to construct valid parameter values beyond the schema's syntactic definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise action statement ('Execute authenticated X (Twitter) API calls'), identifies the resource (X/Twitter), and enumerates capabilities (read data, publish content, manage accounts across 121 endpoints). It explicitly distinguishes from sibling 'explore' by stating xquik is for 'live X/Twitter operation' while explore is for endpoint discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains dedicated 'When to use' and 'When NOT to use' sections that explicitly name sibling tool 'explore' as the prerequisite for discovery and the alternative choice. Clear negative constraints provided ('Do NOT use to discover endpoints', 'Do NOT pass API keys'). Guidelines cover sequencing, authentication boundaries, and operational scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xquik-dev/x-twitter-scraper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server