Skip to main content
Glama
Sign In

TwitterAPI.io MCP Server

by io.github.kaitoInfra
OverviewDiscussionsAdmin

Get Tweet Quotes

get_tweet_quotes
Read-only

Fetch quote-tweets (tweets that quote the given tweetId). Useful for finding commentary on a tweet, measuring reach beyond direct replies. Supports time bounds (sinceTime/untilTime, Unix seconds). Paginates via cursor (~20 per page).

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

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor; omit for first page (~20 per page).
tweetIdYesNumeric ID of the tweet to fetch quote-tweets for.
sinceTimeNoUnix timestamp (seconds) lower bound.
untilTimeNoUnix timestamp (seconds) upper bound.
includeRepliesNoInclude reply-type quote-tweets in addition to top-level. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavioral context by noting pagination via cursor at ~20 per page and optional time bounds, which are useful operational details not in the annotations.

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 sentences, each carrying distinct value: what it does, when it is useful, and how pagination and time bounds work. The core purpose is front-loaded, and there is no redundant or filler content.

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?

Despite lacking an output schema, the description covers the essential call behaviors: quote-tweet retrieval, pagination (~20 per page), time bounds, and the includeReplies option is documented in the schema. It omits minor details like ordering or empty-result behavior, but these are not critical for a read-only fetch 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 description coverage is 100%, so the schema already documents all five parameters clearly. The description mostly reiterates time bounds and pagination behavior without adding new meaning beyond the schema, meeting the baseline for full schema coverage.

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 description opens with a clear verb and resource: 'Fetch quote-tweets (tweets that quote the given tweetId)'. It defines the exact behavior and distinguishes it from reply or retweet tools through the parenthetical, which is essential given the sibling context.

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

Usage Guidelines4/5

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

The description gives a concrete use case: 'finding commentary on a tweet, measuring reach beyond direct replies'. This implies when to use it and signals it is not for direct replies, though it does not explicitly name an alternative sibling like get_tweet_replies.

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

All TwitterAPI.io MCP Server 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