Skip to main content
Glama
Xquik-dev

X Twitter Scraper

by Xquik-dev

xquik

Destructive

Perform live X/Twitter operations including search, user lookup, extraction, and writes with automatic auth and user confirmation. Requires prior endpoint discovery via explore.

Instructions

Send confirmed Xquik API requests across 118 MCP operations.

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, metered operations, 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.

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

  • Read operations return JSON objects with the requested data.

  • Mutating operations require prior user confirmation and return { success: true } or { success: true, warning: '...' }.

  • Pagination responses include has_next_page and next_cursor. Pass cursor as a query param for the next page.

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

Error handling

  • 402: Account access or usage balance requires dashboard attention. Explain the account state and direct the user to the dashboard before retrying.

  • 429: Rate limited. Retry after backoff.

  • 404: Resource not found, such as a missing user, tweet, or monitor.

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

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' } })
Behavior5/5

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

Annotations already provide readOnlyHint=false, destructiveHint=true. The description adds significant behavioral details: only xquik.request() is available, no filesystem/network access, timeouts, response formats for reads and writes, pagination cursors, error handling codes. No contradiction 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?

The description is well-structured with clear sections (When to use, When NOT to use, Behavior, Error handling, Input format, Examples). It is front-loaded with purpose. While lengthy, every section contributes valuable information, making it appropriate for the tool's complexity.

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

Completeness4/5

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

Given the tool's complexity (118 operations, one parameter), the description provides comprehensive context including usage, behavior, error handling, and examples. No output schema, but description mentions return types. Sibling 'explore' handles discovery, making this sufficiently complete.

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 only parameter 'code' is fully described in the schema (100% coverage). The tool description adds examples of valid code and constraints (max length, auth injection). This adds value beyond the schema, justifying a score above the baseline 3.

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 'Send confirmed Xquik API requests across 118 MCP operations.' It identifies the verb 'send' and the resource 'Xquik API requests.' It also distinguishes from the sibling tool 'explore' by specifying that 'explore' should be used 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?

The description includes explicit 'When to use' and 'When NOT to use' sections. It advises using this tool after 'explore' for live operations and confirmation-gated writes, and explicitly states not to use it for endpoint discovery. It also provides the alternative tool 'explore'.

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