Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

get_user_last_tweets

Read-onlyIdempotent

Get a user's recent tweets (~20 per page). Provide userId or userName (userId preferred). For keyword/filter search across X use search_tweets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_last_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response next_cursor. Omit or "" for the first page.
userIdNoNumeric user id (preferred)
userNameNoScreen name without @
includeRepliesNoInclude replies. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, open-world, non-destructive operation, so the description only needs to add context. It adds useful behavioral detail about approximate page size and userId preference, though it does not mention rate limits or detailed return structure.

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, front-loaded with the core action, then parameter guidance, then the alternative tool. There is no wasted wording.

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 read-only timeline tool with fully documented parameters and no output schema, the description covers the essential context. It explains page behavior, identifier choice, and when to use the sibling search tool instead.

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 all four parameters are already documented. The description reinforces the userId-or-userName choice and preference, but adds little beyond the schema's own descriptions.

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 states a specific verb and resource: get a user's recent tweets. It also gives scope (~20 per page) and explicitly distinguishes this from keyword/filter search by naming search_tweets.

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?

It tells the agent to provide userId or userName, with userId preferred, and explicitly routes keyword/filter searches to search_tweets. That gives a clear when-to-use and alternative condition.

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