Skip to main content
Glama

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.

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor for paginating through results. Leave empty for the first page.
tweetIdNoThe 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. 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"
  2. 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: +[]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds useful behavior: page size (20 per page), cursor pagination, the Relevance default, and a usage-based billing note. It stops short of disclosing rate limits or quota behavior, but covers more than the annotations do.

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-relevant content is two tight, front-loaded sentences with zero waste. The injected pricing block is boilerplate that dilutes the payload slightly but is small relative to the whole.

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 need no explanation; the description correctly just notes they are full tweet objects with engagement counts. Pagination, defaults, sort semantics, the sibling relationship, and billing are all covered, so nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds semantic meaning beyond the schema by explaining what Relevance, Latest, and Likes actually surface. That is genuine interpretation, not restatement of the enum.

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') and immediately distinguishes itself from the sibling get_twitter_tweet_replies by naming the ordering control. An agent can tell the two apart 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?

Explicitly says to use this instead of `get_twitter_tweet_replies` 'whenever ordering matters' and explains what each ordering buys you ('Likes surfaces the community's top responses, Latest gives a live view'). The alternative and the selecting condition are both named.

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