AIsa X / Twitter

Get Tweet Replies

get_twitter_tweet_replies

Read-onlyIdempotent

Get the direct replies to a tweet, cursor-paginated. Use this to read the discussion under a post — sentiment, corrections, or follow-up questions. Returns full tweet objects with engagement counts. Prefer get_twitter_tweet_replies_v2 when you want to control ordering (Relevance, Latest, or Likes); this v1 endpoint returns the default order only. To follow a conversation upward to its root instead of downward, use get_twitter_tweet_thread_context.

Usage-based billing; Default request estimate: $0.01335 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_replies"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Cursor for pagination.
`tweetId`	Yes	The tweet ID to get replies for.
`queryType`	No	Sort order for replies. Default is Relevance. Provider reference (supplier schema): `{"default":"Relevance","type":"string"}`.

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"
+]
```

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / cursor / description
```
Added value: +"Cursor for pagination."
```

addedInput schema / properties / queryType

Added value: +{
+  "description": "Sort order for replies. Default is Relevance.\n\nProvider reference (supplier schema): `{\"default\":\"Relevance\",\"type\":\"string\"}`.",
+  "enum": [
+    "Latest",
+    "Likes",
+    "Relevance"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tweetId / description
```
Added value: +"The tweet ID to get replies for."
```

Changed3 schema fields changedOct 15, 2026
- removedInput schema / properties / cursor / description
```
Removed value: -"Cursor for pagination."
```
- removedInput schema / properties / tweetId / description
```
Removed value: -"The tweet ID to get replies for."
```
- 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 declare readOnly/idempotent/openWorld/non-destructive, so the safety bar is covered. The description adds genuinely new behavior: cursor pagination, return shape ("full tweet objects with engagement counts"), and a cost estimate with an explicit caveat that it is not a fixed price. Missing only rate-limit or result-count caps.

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?

Front-loaded with the action, followed by use case, return shape, and routing — a logical order with no filler sentences. The appended HTML-commented pricing block is boilerplate noise but does carry billing information, so it is defensible rather than wasteful.

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, annotations, and fully documented params, the description only needs to add routing and return-shape context, which it does. The one gap is that the stated "default order only" limitation is left unreconciled with the exposed `queryType` parameter.

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 the baseline is 3 and the schema already explains `tweetId`, `cursor`, and the `queryType` enum. However, the description says this endpoint "returns the default order only," which conflicts with the schema exposing a `queryType` enum (Latest/Likes/Relevance) — an agent may be unsure whether `queryType` does anything here.

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?

Names a specific verb and resource ("Get the direct replies to a tweet") and adds the pagination model. It explicitly distinguishes itself from two siblings by name, `get_twitter_tweet_replies_v2` and `get_twitter_tweet_thread_context`, so the agent can pick correctly without reading schemas.

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 concrete when-to-use framing ("read the discussion under a post — sentiment, corrections, or follow-up questions") plus explicit routing rules: use v2 when you need ordering control, use thread_context to walk up to the root. Both alternatives and their selecting conditions are stated.

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?