twitter-threadRead an entire tweet thread/conversation.
| Name | Required | Description | Default |
|---|---|---|---|
| tweet | Yes | Tweet URL or ID of any tweet in the thread | |
| cursor | No | Pagination cursor from a previous response | |
| text_only | No | If true, return only id and text per tweet to save tokens. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety traits are known. The description adds 'entire' and 'conversation' but doesn't disclose pagination behavior, rate limits, or what exactly counts as a conversation (e.g., replies vs. quotes).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no filler words. It is appropriately sized for a straightforward read operation and front-loads the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema and the existence of sibling tools, the one-line description is somewhat sparse. It doesn't mention return format, pagination behavior, or how to differentiate this from twitter-read, leaving room for interpretation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with descriptions for all three parameters: tweet (URL/ID), cursor (pagination), and text_only (token-saving mode). The tool description adds no extra parameter semantics beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses a specific verb ('Read') and a distinct resource ('entire tweet thread/conversation'), making its purpose immediately clear. This distinguishes it from sibling tools like twitter-read (single tweet) and twitter-search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description states what the tool does but leaves the choice of tool entirely to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is uniquely distinguished by platform prefix (reddit vs twitter) and specific action (get a post, get posts, search, etc.). No two tools have overlapping purposes, even within the same platform.
Tool names consistently use lowercase with underscores and a platform prefix, but the pattern is slightly mixed: Reddit tools use 'get' and 'search' as verbs, while Twitter tools include nouns like 'news', 'thread', and 'user-tweets' alongside verbs. Still, names are predictable and readable.
With 10 tools covering two major social platforms, the count is well-scoped. Each tool serves a distinct, meaningful purpose, and no tool feels redundant or unnecessary.
The tool set provides strong read coverage for both Reddit and Twitter, including search, post/thread retrieval, and user timelines. However, it lacks any write or interaction capabilities (e.g., posting, commenting, liking), which is a notable gap for a social media server and could limit agent workflows.