Skip to main content
Glama
Xquik-dev

X Twitter Scraper

by Xquik-dev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

explore

Read-onlyIdempotent

Search and browse the X Twitter API specification to find the right endpoint, parameters, and response shape before making live calls.

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 included usage or requires account access.

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 118 MCP operations.

  • Included usage and does not require authentication.

  • Returns the result of your filter function, such as an empty array if no endpoints match.

  • Returns a validation error if the request function is invalid.

  • Timeout: 60 seconds.

  • Each EndpointInfo contains method, path, summary, category, free, parameters, and responseShape fields.

Input format

Provide a bounded request function. The server exposes spec.endpoints (EndpointInfo[]). Filter, search, or return them.

Examples

Find all included-usage 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
codeYesBounded request 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')

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations declare read-only, idempotent, nondestructive. The description adds details: no network calls, in-memory catalog, free usage, no auth required, validation errors, timeout, and endpoint structure. No contradiction.

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

Conciseness5/5

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

Well-organized with clear headings and sections. Each sentence adds value, no fluff. Information is front-loaded with the main purpose.

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 tool complexity (one parameter, rich annotations, no output schema), the description fully covers behavior, input format, examples, error handling, timeout, and endpoint structure. No gaps.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the 'code' parameter's meaning (bounded request function), how to use spec.endpoints, and providing multiple examples, going beyond the schema.

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: to search and browse the X/Twitter API specification (a specific resource) before making live calls with 'xquik'. It uses specific verbs and differentiates from the sibling tool.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance: use first, before xquik; avoid for live data or if already know endpoint. The relationship with 'xquik' is well explained.

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