AIsa X / Twitter

Get Tweets By IDs

get_twitter_tweets

Read-onlyIdempotent

Fetch the full content of specific tweets when you already know their numeric tweet IDs (accepts multiple IDs in one call). Use this to expand IDs surfaced by search, timelines, or replies into complete objects. Returns text, author, source client, language, creation time, and engagement counts (likes, retweets, replies, quotes, bookmarks, views). If you do not have IDs yet, start with get_twitter_tweet_advanced_search.

Usage-based billing; Default request estimate: $0.0075 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": {
      "tweet_ids": "<tweet_ids>"
    },
    "name": "get_twitter_tweets"
  }
}

Input Schema

Name	Required	Description	Default
`tweet_ids`	Yes	Comma-separated list of tweet IDs.

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: +[
+  "tweet_ids"
+]
```
Changed1 schema field changedOct 19, 2026
- addedInput schema / properties / tweet_ids / description
```
Added value: +"Comma-separated list of tweet IDs."
```
Changed4 schema fields changedOct 15, 2026
- removedInput schema / properties / tweet_ids / description
```
Removed value: -"Comma-separated list of tweet IDs."
```
- removedInput schema / properties / tweet_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
- changedInput schema / properties / tweet_ids / type
```
Previous value: -"array"New value: +"string"
```
- changedInput schema / required
```
Previous value: -[
-  "tweet_ids"
-]New value: +[]
```
First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds that multiple IDs can be passed in one call and includes a per-request cost estimate, but its enumeration of returned fields is redundant given an output schema exists, and it says nothing about behavior for deleted, protected, or invalid IDs.

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?

Front-loaded with the core purpose and the routing rule, in three tight sentences. The middle sentence listing return fields largely duplicates the output schema, and the appended pricing boilerplate adds bulk that isn't about tool selection.

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 annotations, a full-coverage schema, and an existing output schema, the definition covers what an agent needs to pick and call the tool correctly. The remaining gap — how partial or missing IDs are handled — is minor but real for a batch-by-ID fetch.

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 100% and the single parameter is documented as a comma-separated list of tweet IDs. The description's note that it 'accepts multiple IDs in one call' restates that formatting rather than adding limits, maximum batch size, or ID validation rules, so it stays at the baseline.

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 ('Fetch the full content of specific tweets') and immediately constrains it to the case where numeric tweet IDs are already known. This clearly separates it from ID-discovery siblings like get_twitter_tweet_advanced_search.

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 it to 'expand IDs surfaced by search, timelines, or replies into complete objects' and names the alternative to start with when no IDs exist ('If you do not have IDs yet, start with get_twitter_tweet_advanced_search'). Both the when and the fallback are 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?