AIsa X / Twitter

Get Tweet Thread Context

get_twitter_tweet_thread_context

Read-onlyIdempotent

Reconstruct the conversation around a tweet. Accepts either a reply or an original tweet and returns the surrounding thread, cursor-paginated. Use this when a tweet lacks context on its own and you need the parent chain to interpret it correctly. Returns tweets under tweets with has_next_page and next_cursor. For only the replies below a post use get_twitter_tweet_replies_v2.

Usage-based billing; Default request estimate: $0.00555 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tweetId": "<tweetId>"
    },
    "name": "get_twitter_tweet_thread_context"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	The cursor to paginate through the results. First page is empty.
`tweetId`	Yes	The tweet ID to get. Can be a reply tweet or an original tweet.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "tweetId"
+]
```

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / cursor / description

Added value: +"The cursor to paginate through the results. First page is empty."

addedInput schema / properties / tweetId / description

Added value: +"The tweet ID to get. Can be a reply tweet or an original tweet."

Changed3 schema fields changedOct 15, 2026

removedInput schema / properties / cursor / description

Removed value: -"The cursor to paginate through the results. First page is empty."

removedInput schema / properties / tweetId / description

Removed value: -"The tweet ID to get. Can be a reply tweet or an original tweet."

changedInput schema / required

Previous value: -[
-  "tweetId"
-]New value: +[]

First observedSep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the safety profile is free; the description adds genuine behavior — that the result is cursor-paginated and that both reply and original tweets are valid inputs, which matters for interpreting results. It also states the return envelope (`tweets`, `has_next_page`, `next_cursor`), though that partly duplicates the output schema. The injected pricing note discloses billing but is boilerplate rather than tool-specific behavior.

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?

Three tight sentences, front-loaded with the action, then the when-to-use, then the return shape and sibling pointer — every sentence earns its place. The appended pricing block is injected boilerplate that dilutes the otherwise clean structure.

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?

With an output schema present, the description needn't explain return values, yet it still names the response fields; combined with explicit input-type and alternative-tool guidance, an agent has what it needs to call this correctly. Only minor gaps remain, such as whether pagination is required to assemble a full thread.

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% and both parameters are documented there, so the baseline is 3. The description restates the tweetId flexibility already in the schema ('can be a reply tweet or an original tweet') and says nothing new about cursor usage or how many tweets a page contains.

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?

Opens with a specific verb+resource: 'Reconstruct the conversation around a tweet,' and immediately scopes the input ('accepts either a reply or an original tweet'). It is clearly distinguishable from the sibling get_twitter_tweet_replies_v2, which it names.

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?

'Use this when a tweet lacks context on its own and you need the parent chain to interpret it correctly' gives an explicit selection condition, and 'For only the replies below a post use get_twitter_tweet_replies_v2' provides the exclusion/alternative rule. An agent can route between the two tools without opening either schema.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?