Social Fetch

List Twitter tweet replies

twitter_tweet_replies_list

Read-only

List replies to a tweet by URL. Pass url (tweet permalink or numeric id), not tweetId/tweetUrl. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Tweet permalink or numeric id.
`link`	No	Alias for `url`. Prefer `url`.
`path`	No	Alias for `url`. Prefer `url`.
`sort`	No	Alias for `sortBy`. Prefer `sortBy`.
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Ignored if this tool does not support it.
`cursor`	No	Opaque pagination cursor returned by a previous response.
`offset`	No	Ignored if this tool does not support it.
`sortBy`	No	Reply sort order. Defaults to `relevance`.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`tweetId`	No	Alias for `url`. Prefer `url`.
`pageSize`	No	Ignored if this tool does not support it.
`tweetUrl`	No	Alias for `url`. Prefer `url`.
`tweet_id`	No	Alias for `url`. Prefer `url`.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`permalink`	No	Alias for `url`. Prefer `url`.
`tweet_url`	No	Alias for `url`. Prefer `url`.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`conversation_id`	No	Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedSep 21, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / link / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / link / type
```
Removed value: -"string"
```

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `url`. Prefer `url`."
+}

addedInput schema / properties / permalink / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / permalink / type
```
Removed value: -"string"
```

addedInput schema / properties / sort

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `sortBy`. Prefer `sortBy`."
+}

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / tweetId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetId / type
```
Removed value: -"string"
```

addedInput schema / properties / tweetUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_id / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_url / type
```
Removed value: -"string"
```

Changed9 schema fields changedSep 12, 2026

addedInput schema / properties / link

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / permalink

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / sortBy

Added value: +{
+  "description": "Reply sort order. Defaults to `relevance`.",
+  "enum": [
+    "relevance",
+    "recency",
+    "likes"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tweetId

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweetUrl

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_id

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_url

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

changedInput schema / properties / url / description

Previous value: -"Tweet permalink or identifier."New value: +"Tweet permalink or numeric id."

changedInput schema / required

Previous value: -[
-  "url",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJul 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds useful behavior: the canonical url parameter must be preferred over aliases, and the result is a list requiring cursor-based pagination. This is especially valuable because there is no output schema.

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?

Three short sentences with no filler; the most important selection constraint (pass `url`, not aliases) is front-loaded, and each sentence adds necessary information.

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?

For a read-only list tool with a dense 20-parameter schema and no output schema, the description covers the core invocation details: input form, return type, and pagination. It could briefly mention the required context/llm_model parameters or empty-result behavior, but those are at least visible in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds meaning by directing the agent to use `url` rather than the alias parameters and by explaining when to use the cursor. It does not enumerate every alias, but the schema already documents those.

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?

The verb 'List' plus the precise resource 'replies to a tweet' clearly states what the tool does, and this inherently distinguishes it from sibling tools like twitter_tweet_quotes_list and twitter_tweet_retweets_list. It also clarifies the input form ('by URL').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Where to use it is implied by 'replies to a tweet,' but no alternatives are named and no explicit when-to-use versus other Twitter listing tools is given. The pagination tip ('use cursor when paginated') is the only actionable usage guidance.

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

All Social Fetch 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.

List Twitter tweet replies

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources