Skip to main content
Glama
Sign In

AIsa X / Twitter

by one.aisa
OverviewDiscussionsAdmin

Get Tweet Replies V2

get_twitter_tweet_replies_v2
Read-onlyIdempotent

Get replies to a tweet with control over sort order — Relevance (default), Latest, or Likes — 20 per page, cursor-paginated. Use this instead of get_twitter_tweet_replies whenever ordering matters: Likes surfaces the community's top responses, Latest gives a live view of an unfolding thread. Returns full tweet objects with engagement counts.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor for paginating through results. Leave empty for the first page.
tweetIdYesThe tweet ID to get replies for. e.g. 1846987139428634858
queryTypeNoSort order for replies. Default is Relevance. Provider reference (supplier schema): `{"default":"Relevance","enum":["Relevance","Latest","Likes"],"type":"string"}`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "tweetId"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Cursor for paginating through results. Leave empty for the first page.",
+  "type": "string"
+}
    • addedInput schema / properties / queryType / description
      Added value: +"Sort order for replies. Default is Relevance.\n\nProvider reference (supplier schema): `{\"default\":\"Relevance\",\"enum\":[\"Relevance\",\"Latest\",\"Likes\"],\"type\":\"string\"}`."
    • addedInput schema / properties / tweetId / description
      Added value: +"The tweet ID to get replies for. e.g. 1846987139428634858"
  3. Changed6 schema fields changed
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Cursor for paginating through results. Leave empty for the first page.",
-  "type": "string"
-}
    • removedInput schema / properties / queryType / default
      Removed value: -"Relevance"
    • removedInput schema / properties / queryType / description
      Removed value: -"Sort order for replies. Default is Relevance."
    • removedInput schema / properties / queryType / enum
      Removed value: -[
-  "Relevance",
-  "Latest",
-  "Likes"
-]
    • removedInput schema / properties / tweetId / description
      Removed value: -"The tweet ID to get replies for. e.g. 1846987139428634858"
    • changedInput schema / required
      Previous value: -[
-  "tweetId"
-]New value: +[]
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds operational context they don't: 20 results per page, cursor-based pagination, and full tweet objects with engagement counts. The pricing note also discloses usage-based billing and an estimated per-request cost, which is real behavioral context; it stops short of the full range only because rate limits/backfill behavior aren't mentioned.

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?

The tool-specific prose is two dense, front-loaded sentences: capability first, then the sibling alternative and its use cases. The appended pricing block is boilerplate but non-redundant cost information; without it the description would be a clean 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be spelled out, yet the description still signals 'full tweet objects with engagement counts.' Pagination behavior, page size, sort semantics, and the sibling distinction are all covered for a 3-parameter read tool.

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?

With 100% schema coverage the baseline is 3, but the description goes beyond the schema by attaching intent to `queryType` values (Likes surfaces top responses, Latest gives a live view) and by noting the 20-per-page cadence that motivates `cursor`. That adds genuine selection meaning rather than restating enums.

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 replies to a tweet) plus the differentiating capability (control over sort order: Relevance/Latest/Likes). It explicitly names the sibling `get_twitter_tweet_replies` as the no-ordering alternative, so an agent can route between the two without opening either 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 a precise selection rule — use this instead of `get_twitter_tweet_replies` whenever ordering matters — and then explains what each order is for (Likes = top community responses, Latest = live unfolding thread). That is explicit when-to-use plus named alternative, the top of the scale.

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 toolsInspect
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