twitterapi-io-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_twitterapi_docsA | Search TwitterAPI.io documentation: API endpoints, guides (pricing, rate limits, filter rules), and blog posts. USE THIS WHEN: You need to find information across the entire documentation. RETURNS: Ranked results with endpoint paths, descriptions, and relevance scores. Examples:
|
| get_twitterapi_endpointA | Get complete documentation for a specific TwitterAPI.io endpoint. USE THIS WHEN: You know the exact endpoint name (e.g., from search results). RETURNS: Full details including path, parameters, cURL example, and code snippets. Common endpoints:
|
| list_twitterapi_endpointsA | List all TwitterAPI.io API endpoints organized by category. USE THIS WHEN: You need to browse available endpoints or find endpoints by category. CATEGORIES: user, tweet, community, webhook, stream, action, dm, list, trend RETURNS: Endpoint names with HTTP method and path for each category. |
| get_twitterapi_guideA | Get a TwitterAPI.io page from the offline snapshot by page key. USE THIS WHEN: You need the full content of a specific page (guides, docs, policies, contact, etc.). TIP: Use search_twitterapi_docs if you don't know the page key. RETURNS: Full guide content with headers, paragraphs, and code examples. |
| get_twitterapi_urlA | Fetch a TwitterAPI.io or docs.twitterapi.io URL. USE THIS WHEN: You have a specific link and want its full content. RETURNS: Parsed content from the offline snapshot. If not found, you can set fetch_live=true (restricted to twitterapi.io/docs.twitterapi.io). |
| get_twitterapi_pricingA | Get TwitterAPI.io pricing information: credit system, endpoint costs, QPS limits. USE THIS WHEN: You need to know API costs, credit calculations, or rate limits. RETURNS: Pricing tiers, credit costs per endpoint, QPS limits by balance level. |
| get_twitterapi_authA | Get TwitterAPI.io authentication guide: API key usage, headers, code examples. USE THIS WHEN: You need to set up authentication or see request examples. RETURNS: API key header format, base URL, cURL/Python/JavaScript examples. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All TwitterAPI.io Documentation | 67 endpoints + guide pages + blog posts |
| API Endpoint List | Summary of all API endpoints |
| API Endpoints (Alias) | Alias of twitterapi://docs/endpoints |
| Guide Pages | Pricing, QPS limits, filter rules, etc. |
| Pricing Guide | Credit system, endpoint costs, QPS limits |
| Authentication Guide | API key setup, headers, code examples |
| Rate Limits Guide | QPS limits by balance level |
| Rate Limits Guide (Alias) | Alias of twitterapi://guides/qps_limits |
| Tweet Filter Rules | Advanced search filter syntax |
| Tweet Filter Rules (Alias) | Alias of twitterapi://guides/tweet_filter_rules |
| Changelog | API changelog |
| Introduction | Overview of TwitterAPI.io |
| README | Project overview and usage |
| Server Metrics | Performance metrics, SLO tracking, cache stats |
| Health Check | Server health status and data freshness |
| Data Freshness | Last docs update time and freshness status |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: authentication, specific endpoint docs, page content, pricing, URL fetching, listing endpoints, and searching docs. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscore (get_, list_, search_) and include 'twitterapi' for context. No mixing of conventions.
7 tools is well-scoped for a documentation-focused server. Each tool provides a necessary function without redundancy, and the count is appropriate for the domain.
The tool set covers core documentation needs: auth, endpoint details, pricing, search, and listing. Minor gaps like error codes or changelog, but the surface is largely complete.