Skip to main content
Glama
Xquik-dev

X Twitter Scraper

by Xquik-dev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

explore

Read-onlyIdempotent

Search the X Twitter API specification to find endpoints, parameters, and response shapes before making live API 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 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 113 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 | media | monitoring | support | twitter | x-accounts | x-write), 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')

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations already mark it as readOnlyHint, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral details: no network calls, always free, no authentication, returns result of filter function or error, 60-second timeout, and lists what each EndpointInfo contains. This goes well beyond the 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 sections, bullet points, and examples. It is moderately lengthy but every sentence serves a purpose. Minor deduction because some information (e.g., example functions) could be slightly condensed, but overall it is clear 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 (1 parameter, no output schema), the description is thorough. It covers the return shape (EndpointInfo fields), error behavior, timeout, and sandbox details. No gaps are apparent for an agent to use the tool correctly.

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 input schema has 1 parameter ('code') with 100% coverage. The description adds significant value by explaining the parameter's format (async arrow function), the sandbox environment (spec.endpoints), and providing multiple examples. This extra context justifies a score above 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 explicitly states the tool's purpose: 'Search and browse the Xquik X (Twitter) API specification to discover endpoints before making live API calls with the 'xquik' tool.' It uses specific verbs ('search and browse') and clearly distinguishes itself from the sibling tool 'xquik' by stating it is for discovery, not live data.

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 dedicated 'When to use' and 'When NOT to use' sections. It advises using 'explore' first to find endpoints before calling 'xquik' and explains when not to use it (e.g., if already know the endpoint or need live data). This provides explicit guidance and alternatives.

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