AIsa X / Twitter

Get Tweet Quotations

get_twitter_tweet_quotes

Read-onlyIdempotent

Get quote tweets of a given tweet — posts that embedded it with added commentary — cursor-paginated. Use this to see how a post is being reframed or argued about, which is often more revealing than plain replies. Returns full tweet objects with engagement counts. For direct replies use get_twitter_tweet_replies_v2; for accounts that amplified it without comment use get_twitter_tweet_retweeters.

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

Input Schema

Name	Required	Description
`cursor`	No	Cursor for pagination.
`tweetId`	Yes	The tweet ID to get quotes for.
`sinceTime`	No
`untilTime`	No
`includeReplies`	No	Whether to include replies in the results. Default is True. Provider reference (supplier schema): `{"default":true,"type":"boolean"}`.

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

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Cursor for pagination.",
+  "type": "string"
+}

addedInput schema / properties / includeReplies

Added value: +{
+  "description": "Whether to include replies in the results. Default is True.\n\nProvider reference (supplier schema): `{\"default\":true,\"type\":\"boolean\"}`.",
+  "type": "boolean"
+}

addedInput schema / properties / sinceTime

Added value: +{
+  "maximum": 9223372036854776000,
+  "minimum": 0,
+  "type": "integer"
+}

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

addedInput schema / properties / untilTime

Added value: +{
+  "maximum": 9223372036854776000,
+  "minimum": 0,
+  "type": "integer"
+}

Changed3 schema fields changedOct 15, 2026

removedInput schema / properties / cursor

Removed value: -{
-  "description": "Cursor for pagination.",
-  "type": "string"
-}

removedInput schema / properties / tweetId / description
```
Removed value: -"The tweet ID to get quotes for."
```

changedInput schema / required

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

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is low; the description adds genuinely new traits — cursor pagination and that results are full tweet objects with engagement counts — plus a billing estimate. It does not mention rate limits or result ordering, which keeps it from a 5.

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 tight sentences in a deliberate order: definition, then motivation, then sibling routing. The only non-authored content is the short pricing block, which is clearly delimited and adds cost context rather than noise.

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, return-value detail is optional, yet the description still summarizes the payload ('full tweet objects with engagement counts'). Pagination and sibling routing are covered; the only real gap is the unexplained time-range filters, a minor omission for a 5-parameter read tool.

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 60%: `sinceTime` and `untilTime` have no schema description at all, and the description never explains them (units, format, or default behavior). It does add the concept of cursor pagination, which maps to `cursor`, but does not compensate for the undocumented time filters.

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 ('Get quote tweets of a given tweet') and immediately defines the concept ('posts that embedded it with added commentary'). It explicitly names the sibling tools it is not (`get_twitter_tweet_replies_v2`, `get_twitter_tweet_retweeters`), so an agent can distinguish it without opening any schema.

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 when-to-use rationale ('to see how a post is being reframed or argued about') and maps the two nearest alternatives to their distinct conditions: direct replies vs. comment-free amplification. Exclusions and routing are both spelled out.

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?