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.

Input Schema

Name	Required	Description	Default
`tweet_ids`	No	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 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.4/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 safety is covered. The description adds real value beyond that: batch acceptance in one call and the exact fields returned (text, author, source client, language, creation time, engagement counts), which helps an agent judge sufficiency before calling.

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 core is front-loaded and tight, with purpose, precondition, alternative and return fields in three economical sentences. The appended pricing boilerplate adds length that serves billing context rather than tool selection, a minor deduction.

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?

For a simple ID-expansion lookup with full schema coverage, an output schema, and rich annotations, the description supplies everything an agent needs: precondition, batch behavior, alternative entry point, and field coverage.

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?

Only one parameter and schema coverage is 100%, so the schema already documents the comma-separated ID format. The description's note that multiple IDs are accepted in one call adds a small amount of batch semantics but nothing about limits or ordering; baseline 3 applies.

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 (Fetch) and resource (full content of specific tweets) plus the precondition (you already know their numeric IDs). It also names the sibling `get_twitter_tweet_advanced_search` as the contrasting entry point, so an agent can place it without opening the 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 explicit when-to-use (you already have IDs) and when-not-to-use (if you do not have IDs yet), routing the agent to the correct alternative by name. The 'expand IDs surfaced by search, timelines, or replies' line clarifies its role in a workflow.

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?