twitterapi-docs-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
Server capabilities have not been inspected yet.
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 TwitterAPI.io guide pages for conceptual topics. USE THIS WHEN: You need information about pricing, rate limits, authentication, or filter rules. AVAILABLE GUIDES: pricing, qps_limits, tweet_filter_rules, changelog, introduction, authentication, readme RETURNS: Full guide content with headers, paragraphs, and code examples. |
| 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 | 52 endpoints + guide pages + blog posts |
| API Endpoint List | Summary of all API 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 |
| Tweet Filter Rules | Advanced search filter syntax |
| Server Metrics | Performance metrics, SLO tracking, cache stats |
| Health Check | Server health status and data freshness |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: get_twitterapi_auth handles authentication setup, get_twitterapi_endpoint provides specific endpoint details, get_twitterapi_guide covers conceptual topics, get_twitterapi_pricing focuses on costs and limits, list_twitterapi_endpoints offers a categorized overview, and search_twitterapi_docs enables cross-documentation search. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (e.g., get_twitterapi_auth, list_twitterapi_endpoints, search_twitterapi_docs). The naming is predictable and uniform across all six tools, enhancing readability and usability.
With 6 tools, the server is well-scoped for its purpose of providing documentation access for TwitterAPI.io. Each tool serves a unique and necessary function, from authentication and endpoint details to guides, pricing, listing, and search, covering the domain comprehensively without being overwhelming.
The tool set offers complete coverage for accessing TwitterAPI.io documentation, including authentication, specific endpoints, conceptual guides, pricing, endpoint listings, and search capabilities. There are no obvious gaps; agents can retrieve all necessary information without dead ends, supporting a full range of documentation queries.