TweetAPI MCP

Official

by tweetapi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get User Articles

tweetapi_user_articles

Read-onlyIdempotent

Fetch one page of a user's X Articles posts by numeric user ID, including titles and preview text; pass a post ID to the tweet details tool to read the full article.

Instructions

Fetch one page of the posts that published a user's X Articles, with each Article's title and preview text. The full Article text is not included: pass the post ID to tweetapi_tweet_details to read it. 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.4/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent, but the description adds real operational context beyond them: TweetAPI API key requirement, one request per call costing roughly 1 unit, and a per-result cost estimate. It does not cover error or rate-limit behavior, but for a paged read tool this is substantial added disclosure.

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?

Five short sentences, each carrying distinct information: scope, exclusion, auth and cost, and pagination. Key constraints are front-loaded and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return-shape explanation is unnecessary, and the description covers scope, paging, cost, and prerequisites. A small gap remains around ordering or page-size behavior, but an agent has what it needs to call it correctly.

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 coverage is 100%, so cursor, userId, and responseFormat are already documented in the schema, including the username-lookup guidance. The description's cursor sentence largely restates the schema and adds no new format or constraint detail, so 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: 'Fetch one page of the posts that published a user's X Articles,' plus the exact payload (title and preview text). This clearly separates it from sibling listing tools like tweetapi_user_tweets.

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 states a limitation ('full Article text is not included') and routes the agent to tweetapi_tweet_details with the post ID for the full text. Continuation is spelled out ('to get the next one, call again with cursor set to this result's completeness.nextCursor').

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

Deploy Server