Skip to main content
Glama
Xquik-dev

X Twitter Scraper

explore

Read-onlyIdempotent

:

Instructions

Search and browse the Xquik X (Twitter) API specification to discover endpoints before making live API calls with the 'xquik' tool.

When to use

  • Use 'explore' FIRST to find the right endpoint path, parameters, and response shape before calling 'xquik'.

  • Use when the user asks what capabilities are available or how to accomplish a task on X/Twitter.

  • Use to check whether an endpoint is free or requires a subscription.

When NOT to use

  • Do NOT use 'explore' to fetch live data from X — use 'xquik' instead.

  • Do NOT use if you already know the endpoint path and parameters.

Behavior

  • Read-only, idempotent. No network calls — runs against an in-memory catalog of 121 endpoints.

  • Always free, no authentication or credits required.

  • Returns the result of your filter function (e.g., empty array if no endpoints match).

  • Returns an error message if the code is syntactically invalid or throws at runtime.

  • Execution timeout: 60 seconds.

  • Each EndpointInfo contains: method, path, summary, category (account | composition | credits | extraction | integrations | media | monitoring | support | twitter | x-accounts | x-write | bot), free (boolean), parameters (array), and responseShape (string).

Input format

Write an async arrow function. The sandbox provides spec.endpoints (EndpointInfo[]). Filter, search, or return them.

Examples

Find all free endpoints: async () => spec.endpoints.filter(e => e.free) Find by category: async () => spec.endpoints.filter(e => e.category === 'composition') Search by keyword: async () => spec.endpoints.filter(e => e.summary.toLowerCase().includes('tweet')) Get full details: async () => spec.endpoints.find(e => e.path === '/api/v1/x/tweets/search')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript async arrow function that filters or searches spec.endpoints (EndpointInfo[]). Must return an array or single EndpointInfo object. Example: async () => spec.endpoints.filter(e => e.category === 'twitter')
Behavior5/5

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

While annotations indicate read-only/idempotent status, the description adds substantial critical execution context: 'No network calls — runs against an in-memory catalog', 'Always free, no authentication', 60-second timeout, runtime error handling behavior, and detailed EndpointInfo return structure (method, path, free boolean, etc.).

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?

Though lengthy, content is well-structured with markdown headers (## When to use, ## Behavior, ## Examples) making it scannable. Every section serves a critical purpose for this complex code-execution tool; however, the length prevents a perfect score for conciseness.

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?

Absence of output schema is adequately compensated by detailed description of return values (result of filter function, EndpointInfo object contents including method, path, category, free status, parameters, responseShape) and error scenarios. Distinguishes from sibling tool completely.

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% providing baseline documentation for the 'code' parameter. Description adds significant semantic value through the 'Input format' section explaining the sandbox environment provides `spec.endpoints`, and four concrete examples demonstrating different filtering patterns (by free status, category, keyword, specific path lookup).

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?

Description explicitly states the tool 'Search[es] and browse[s] the Xquik X (Twitter) API specification to discover endpoints' and clearly distinguishes it from sibling tool 'xquik' (discover vs. live API calls). Uses specific verbs and identifies the exact resource (API specification/endpoints).

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 direct users to call 'explore' FIRST before 'xquik', list specific scenarios (finding capabilities, checking subscription requirements), and explicitly prohibit using it for live data fetch or when endpoint details are already known.

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