TweetAPI MCP

Official

by tweetapi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get User Photos

tweetapi_user_photos

Read-onlyIdempotent

Retrieve one page of a user's photo posts, like their profile Photos tab, using a numeric user ID; use the returned cursor to fetch subsequent pages.

Instructions

Fetch one page of a user's posts that contain photos, as on the Photos tab of their profile. Videos are a separate feed: use tweetapi_user_videos. 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?

Beyond the annotations (readOnly/idempotent/openWorld), it discloses the auth requirement (TweetAPI API key), the cost model (one request per call, usually 1 unit, with a per-result cost estimate), and pagination behavior. 'Read-only' merely restates the annotation, and it says nothing about error or rate-limit behavior, so it stops just short of full transparency.

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 tight sentences, front-loaded with the purpose, then the sibling exclusion, then cost/prerequisites, then pagination. Nothing is redundant with the schema and no sentence is wasted.

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, return values need not be explained, and the description still covers the decisions an agent must make: which sibling to use, whether auth is needed, what a call costs, and how to continue paging.

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 fully documented in the schema. The description only restates the cursor continuation semantics and adds no new meaning about userId resolution or the full/compact tradeoff, 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?

States a specific verb and resource ('Fetch one page of a user's posts that contain photos') plus a concrete mental model ('as on the Photos tab of their profile'). It immediately carves out the boundary against the nearest sibling by naming tweetapi_user_videos for video content.

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?

Gives an explicit routing rule: videos are a separate feed, use tweetapi_user_videos. It also gives the continuation rule ('call again with cursor set to this result's completeness.nextCursor'), which tells the agent exactly how to page rather than guessing.

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

Deploy Server