TweetAPI MCP

Official

by tweetapi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Verified Followers

tweetapi_user_verified_followers

Read-onlyIdempotent

Fetches one page of a user's verified followers for reviewing which verified accounts follow them, and returns a cursor for retrieving the next page.

Instructions

Fetch one page of a user's followers who are verified accounts, as on the Verified Followers tab. For all followers, use tweetapi_user_followers_v2. 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

Behavior4/5

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

Annotations already cover the read-only/idempotent/no-destruction profile, and the description goes beyond them by disclosing the auth requirement, the per-call request count and typical cost of 1 unit, and that results carry a cost estimate. The pagination contract (call again with the returned nextCursor) is spelled out. It stops short of describing failure modes or rate limits, so it is strong rather than exhaustive.

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?

Four compact sentences, front-loaded with the resource and filter, then alternative routing, then cost/auth, then pagination. No hedging or filler; every sentence carries operational information.

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, yet it still flags the cost estimate and completeness.nextCursor fields the agent must consume. For a simple 3-parameter paginated read, nothing needed to invoke it correctly 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 userId, cursor, and responseFormat are fully documented in the schema itself. The description's pagination sentence largely restates the cursor rule already in the schema, adding flow context rather than new parameter meaning; 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?

States a specific verb and resource with a clear filter: 'Fetch one page of a user's followers who are verified accounts,' and anchors it to the product's Verified Followers tab. An agent can distinguish it from generic follower tools without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative ('For all followers, use tweetapi_user_followers_v2'), giving the agent a direct routing rule for the most likely confusion. It also specifies the API-key prerequisite, which gates whether the call is even possible.

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

Deploy Server