TweetAPI MCP

Official

by tweetapi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get User Lists

tweetapi_user_lists

Read-onlyIdempotent

Fetches one page of Lists shown on a user's Lists tab, including Lists owned by other accounts and private Lists with their mode; use the returned cursor to paginate.

Instructions

Fetch one page of the Lists shown on a user's Lists tab. X can include Lists owned by other accounts, so check owner on each List; Private Lists are included and mode says which. For Lists other accounts added this user to, use tweetapi_user_list_memberships. Read-only. Needs a TweetAPI API key and makes one TweetAPI request per call, usually costing 1 unit; each result includes a cost estimate. Returns one page: to get the next one, call again with cursor set to this result's completeness.nextCursor.

Input Schema

Name	Required	Description
`cursor`	No	completeness.nextCursor from the previous page. Omit it for the first page.
`userId`	Yes	Numeric user ID. This tool does not look up usernames; call tweetapi_user_by_username first if you only have a username or profile link.
`responseFormat`	No	full (default) returns TweetAPI's JSON unchanged. compact keeps full post text, IDs, links, original dates, counts, and cursors but drops bulky fields; output.fieldsOmitted lists what was dropped.

Output Schema

Name	Required	Description
`cost`	Yes
`mode`	Yes
`tool`	Yes
`notice`	Yes
`output`	Yes
`result`	Yes
`endpoint`	Yes
`usageDocs`	No
`pagination`	No	Pagination exactly as TweetAPI returned it.
`statusCode`	Yes
`retrievedAt`	Yes	When the MCP server received this response (ISO 8601). Not the post or profile date, and not a promise that X's data was fresh at that moment.
`completeness`	Yes
`resolvedInput`	No	Identifiers the MCP server parsed from links or @handles before calling TweetAPI.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.3Nov 5, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"completeness.nextCursor from the previous page. Omit it for the first page."
```
Addedv0.2.1Nov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses that private Lists are included and flagged by a mode field, that ownership must be verified because X surfaces Lists owned by other accounts, that each call costs roughly 1 unit with a cost estimate in the result, and that an API key is required. That is materially more than the annotations provide.

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?

Purpose comes first, then the sibling exclusion, then safety/auth/cost, then pagination — a deliberate order with no filler. Every clause carries information an agent needs to call the tool correctly.

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?

With an output schema present, the description need not explain return values, and it covers the remaining gaps: auth, cost model, private-List visibility, ownership caveat, and how to page. Nothing essential to 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%, so all three parameters are already documented in the schema, including the cursor provenance and the full/compact trade-off. The description restates the pagination mechanics (cursor set to completeness.nextCursor) rather than adding new semantics, so the baseline of 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 plus scope: 'Fetch one page of the Lists shown on a user's Lists tab.' It immediately disambiguates the adjacent resource by noting that memberships (Lists other accounts added this user to) live in a different tool, so an agent can separate this from tweetapi_user_list_memberships without reading schemas.

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?

It names a concrete alternative (tweetapi_user_list_memberships) with the condition that selects it, and the userId parameter steers agents to tweetapi_user_by_username when only a handle is available. It stops short of distinguishing this from list-oriented siblings such as tweetapi_list_search or tweetapi_list_details, leaving some selection ambiguity.

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

Deploy Server