TweetAPI MCP

Official

by tweetapi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Following List

tweetapi_user_following_list

Read-onlyIdempotent

Fetch a page of profiles a user follows, with optional count and cursor pagination to continue through additional pages.

Instructions

Fetch one page of profiles a user ID follows, with an optional count to set the page size. Use tweetapi_user_following_ids when you only need IDs. 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
`count`	No	Page size from 1 to 500. Omit it for the default.
`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.

Changed2 schema fields changedv0.3.3Nov 5, 2026

addedInput schema / properties / count / description

Added value: +"Page size from 1 to 500. Omit it for the default."

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.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds non-obvious operational context: requires a TweetAPI API key, one request per call, roughly 1 unit cost, and a cost estimate embedded in each result. It also discloses pagination semantics tied to completeness.nextCursor, which is behavior an agent cannot infer from annotations alone.

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?

Front-loads what the tool returns, then alternatives, then cost/auth, then pagination – a sensible order with no filler. The 'optional count to set the page size' clause mildly duplicates the schema's own parameter description but is minor.

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?

For a four-parameter paginated read with an output schema present, the description covers selection, cost, auth, and page continuation. Return-value detail is rightly delegated to the output schema, so nothing an agent needs before calling 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 the baseline is 3. The description restates the count-as-page-size and cursor-continuation meanings already documented in the schema, adding no syntax or format detail beyond it.

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?

States a specific verb and resource ('Fetch one page of profiles a user ID follows') and immediately scopes it as paginated profile data rather than IDs. It explicitly names the sibling tweetapi_user_following_ids as the IDs-only variant, so an agent can route correctly without opening 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?

Gives an explicit alternative-selection rule ('Use tweetapi_user_following_ids when you only need IDs') plus continuation instructions for the next page. It stops short of explaining when to prefer the other close sibling, tweetapi_user_following_v2, and offers no exclusion guidance.

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

Deploy Server