Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

get_user_timeline

Read-onlyIdempotent

Get a user's profile timeline by userId (~20 per page), same order as the X app profile. Requires userId.

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": {
      "userId": "<userId>"
    },
    "name": "get_user_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response next_cursor. Omit or "" for the first page.
userIdYesNumeric user id
includeRepliesNoInclude replies. Default false.
includeParentTweetNoInclude parent tweet when item is a reply. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/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 the bar is lower. The description adds real context beyond them: roughly 20 items per page and the ordering matching the X app profile, which matters for interpreting and continuing the feed. Auth requirements and rate limits are still unstated.

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?

One compact sentence with the resource and ordering front-loaded and a short prerequisite clause; nothing is padded, though the trailing 'Requires userId' partly restates the schema's required field.

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?

For a four-param read-only feed tool with no output schema, the description supplies the essentials: identity param, page size, ordering, and pagination expectation. It omits what a returned item contains and defaults for replies/parent tweets (left to the schema).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3; description adds that a userId is required and gives page-size/order context that the schema lacks. Cursor semantics (omit or '' for first page) are documented in the schema, so the description need not repeat them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a user's profile timeline by userId') plus a scope detail (page size, ordering matching the X app profile). It does not explicitly name a sibling such as get_user_mentions or get_user_last_tweets, so the agent must infer boundaries from the word 'profile timeline'.

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

Usage Guidelines3/5

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

Usage is implied: it is the tool for a user's profile feed and requires userId. There is no explicit when-to-use/when-not guidance and no named alternative for adjacent cases (mentions, last tweets, list timelines).

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