Skip to main content
Glama

AIsa Social

by one.aisa
OverviewDiscussionsAdmin

Get Tweet Thread Context

get_twitter_tweet_thread_context
Read-onlyIdempotent

Reconstruct the conversation around a tweet. Accepts either a reply or an original tweet and returns the surrounding thread, cursor-paginated. Use this when a tweet lacks context on its own and you need the parent chain to interpret it correctly. Returns tweets under tweets with has_next_page and next_cursor. For only the replies below a post use get_twitter_tweet_replies_v2.

Usage-based billing; Default request estimate: $0.00555 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe cursor to paginate through the results. First page is empty.
tweetIdNoThe tweet ID to get. Can be a reply tweet or an original tweet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"The cursor to paginate through the results. First page is empty."
    • addedInput schema / properties / tweetId / description
      Added value: +"The tweet ID to get. Can be a reply tweet or an original tweet."
  2. Changed3 schema fields changed
    • removedInput schema / properties / cursor / description
      Removed value: -"The cursor to paginate through the results. First page is empty."
    • removedInput schema / properties / tweetId / description
      Removed value: -"The tweet ID to get. Can be a reply tweet or an original tweet."
    • changedInput schema / required
      Previous value: -[
-  "tweetId"
-]New value: +[]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds valuable behavioral context: cursor-paginated output and the parent-chain reconstruction behavior. It stops short of noting auth requirements or rate limits, so a 4 is warranted.

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 description is front-loaded and efficient: purpose, trigger, return format, and alternative in four tight sentences. The appended billing note is clearly demarcated but does add non-behavioral length, keeping it just under a 5.

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 covering safety, a full schema, and an output schema present, the description needn't explain return values yet still summarizes them usefully. It covers the key distinctions and pagination behavior; only auth/permission details are absent, which is minor given the read-only annotations.

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 both parameters are fully documented in the schema itself (cursor semantics and the reply/original tweet note for tweetId). The description's 'accepts either a reply or an original tweet' merely echoes the schema's tweetId description, adding no new parameter semantics. Baseline 3 is appropriate.

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 ('Reconstruct the conversation around a tweet') and clarifies its scope by noting it accepts either a reply or an original tweet. It explicitly distinguishes itself from the sibling get_twitter_tweet_replies_v2, so an agent can tell them apart without opening a 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?

Provides an explicit trigger condition ('when a tweet lacks context on its own and you need the parent chain') and names the alternative with its selecting condition ('For only the replies below a post use get_twitter_tweet_replies_v2'). Nothing is left to inference.

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

All AIsa Social 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