Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

get_tweet_replies

Read-onlyIdempotent

Get replies to a tweet (v1). Tweet must be an original post. Up to ~20 per page; use cursor to paginate. Prefer get_tweet_replies_v2 for Relevance/Latest/Likes sorting.

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_tweet_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response next_cursor. Omit or "" for the first page.
tweetIdYesOriginal tweet id (not a reply)
sinceTimeNoUnix timestamp (seconds); on or after
untilTimeNoUnix timestamp (seconds); before

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond them: a ~20-item page size, cursor-based pagination, and the original-post restriction that will cause failures if ignored. It stops short of noting auth needs, rate limits, or what a reply object contains.

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, zero filler, with the version, precondition, and sibling routing front-loaded in that order. Every clause carries operational 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?

With only 4 parameters, full schema coverage, and annotations covering the safety semantics, this is nearly complete for a read-only paged listing. The residual gap is that no output schema exists and the description never characterizes the reply records returned – the one place a description would still be carrying weight.

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 still adds meaning: it ties 'cursor' to pagination flow and quantifies the page size, which the schema does not. It says nothing about how sinceTime/untilTime interact with pagination, leaving a small gap.

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'), marks the API version (v1), and immediately distinguishes it from get_tweet_replies_v2. An agent can tell which of the two replies tools it wants 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 both a precondition ('Tweet must be an original post') and an explicit routing rule: prefer get_tweet_replies_v2 for Relevance/Latest/Likes sorting. That is a concrete when-not plus a named alternative, leaving little to inference.

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

All SupaBird 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