Skip to main content
Glama
Xquik-dev

X Twitter Scraper

by Xquik-dev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

xquik

Destructive

Send confirmed X/Twitter API requests for search, user lookup, writes, and monitors. Requires prior endpoint discovery via explore.

Instructions

Send confirmed Xquik API requests across 100+ REST endpoints.

When to use

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

  • Use for live X/Twitter operations such as tweet search, user lookup, giveaway draws, extraction jobs, composition, private reads, persistent monitors, webhooks, and confirmation-gated writes.

  • Confirm private reads, persistent resources, billing flows, and writes before using endpoints that require user approval.

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

  • Processes the provided request function with xquik.request(path, options?) and spec.endpoints available.

  • No filesystem or arbitrary network access - only xquik.request() is available. Console calls are silently ignored.

  • Timeout: 60 seconds per invocation, 60 seconds per individual API request.

  • Read operations (GET) return JSON objects with the requested data. Mutating operations (POST/PATCH/DELETE) require prior user confirmation and 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.

  • Some operations modify X or Xquik resources. Show the exact payload, target, and cost before calling them.

Error handling

  • 402: Subscription required or insufficient credits. Explain the billing issue and ask before any checkout or top-up action.

  • 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, account info, support, credit balance, and webhook management.

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

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

Input format

Provide a bounded request 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') After explicit user confirmation, post tweet: async () => xquik.request('/api/v1/x/tweets', { method: 'POST', body: { account: '<confirmed_account>', text: '<confirmed_text>' } })

Input Schema

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

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

The description discloses numerous behavioral traits: the request function mechanism, timeout (60s), pagination (has_next_page, next_cursor), read vs write return formats, error handling for 402/429/404/200-warning, and costs. This goes well beyond the annotations (destructiveHint: true) and provides critical context for an agent.

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?

The description is well-structured with clear sections (When to use, When NOT to use, Behavior, Error handling, Costs, Input format, Examples). It is front-loaded with the purpose. While it is relatively long, every section earns its place; minor redundancy could be trimmed but overall it is effective and organized.

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?

Given the tool's complexity (100+ endpoints, multiple behaviors, no output schema) and the rich annotations (openWorldHint: true, destructiveHint: true), the description comprehensively covers usage, behavior, error handling, costs, and pagination. It provides sufficient context for an agent to invoke the tool correctly without relying on an output schema.

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?

The single 'code' parameter is fully described in the schema (100% coverage) with a detailed description and example. The tool description adds further context with input format and multiple examples, enhancing the schema's explanation. However, the schema already does the heavy lifting, so a 4 is appropriate.

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 clearly states the tool's purpose: 'Send confirmed Xquik API requests across 100+ REST endpoints.' It uses a specific verb ('send') and resource ('Xquik API requests'), and distinguishes it from the sibling tool 'explore' by specifying that it should be used after exploration.

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?

The description provides explicit when-to-use (after 'explore', for live operations) and when-not-to-use (not for discovering endpoints, not passing auth). It also details usage contexts for different operations, reads vs writes, and prerequisites like user confirmation.

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