Skip to main content
Glama
TweetAPI MCP

TweetAPI MCP

Official

TweetAPI MCP Tool Catalog

tweetapi_tool_catalog
Read-onlyIdempotent

Lists every TweetAPI tool as JSON with endpoint, cost, formats and input schema, and filters by name, path or category so you can choose the right tool and check costs before live calls.

Instructions

List the tools on this server as JSON: for each, its name, description, category, the TweetAPI endpoint it calls, estimated cost, response formats and input schema. Filter it with toolName, endpointPath or category. Use it to pick the right tool or check costs before calling live tools. Free: uses no API key or units.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tweetapi_tool_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOne of docs, user, tweet, search, list, community, space, trends or account.
toolNameNoExact tool name, such as tweetapi_search, to return only that tool.
endpointPathNoTweetAPI endpoint path, such as /tw-v2/user/followers, to find the tool that calls it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.3
    • addedInput schema / properties / category / description
      Added value: +"One of docs, user, tweet, search, list, community, space, trends or account."
    • addedInput schema / properties / endpointPath / description
      Added value: +"TweetAPI endpoint path, such as /tw-v2/user/followers, to find the tool that calls it."
    • addedInput schema / properties / toolName / description
      Added value: +"Exact tool name, such as tweetapi_search, to return only that tool."
  2. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered without the description. The description adds genuinely new context beyond them: "Free: uses no API key or units," which tells the agent there is zero cost and no credential prerequisite for calling it — a meaningful behavioural fact absent from the structured fields. It does not mention rate limits or result size, keeping it at 4 rather than 5.

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?

Three tight sentences: what it returns, how to filter, and when to use it, plus the free-cost note. Content is front-loaded with the return shape and nothing is repeated or padded.

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?

There is no output schema, but the description compensates by enumerating the returned fields, so an agent knows what to expect. With all three filters optional, zero required parameters, and cost/auth behaviour stated, nothing essential for a correct first call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and each parameter already carries its own description with a concrete example (e.g. /tw-v2/user/followers). The description's "Filter it with toolName, endpointPath or category" only restates the parameter names without adding syntax, matching rules beyond "Exact tool name," or precedence when multiple filters are combined, so the baseline 3 applies.

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 opens with a specific verb and resource ("List the tools on this server as JSON") and enumerates exactly what each entry contains — name, description, category, endpoint, estimated cost, response formats, input schema. That is a precise inventory of a catalog tool, clearly distinct from siblings like tweetapi_endpoint_lookup or tweetapi_docs_search, which operate on endpoints or docs rather than the whole tool set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it to pick the right tool or check costs before calling live tools" gives a clear when-to-use context, and the filter list implies narrowing by name, path or category. It stops short of naming an exclusion or an alternative sibling (e.g. when to prefer tweetapi_endpoint_lookup for a known endpoint), so it is clear but not fully routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.