Skip to main content
Glama

x-twitter

by com.jojapi
OverviewDiscussionsAdmin

@Deprecated favorites are now known as likes.

get_base_apitools_favoritesList

See details https://developer.x.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/get-favorites-list Group: Tweets. Billing per call: 1 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxIdNoReturns results with an ID less than (that is, older than) or equal to the specified ID.
userIdNo
sinceIdNoReturns results with an ID greater than (that is, more recent than) the specified ID. There are limits to the number of Tweets which can be accessed through the API. If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available.
proxyUrlNo
resFormatNo
screenNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations and a description that mentions only billing, there is no disclosure of side effects, rate limits, required authentication, or other behavioral traits. The tool's runtime behavior is completely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely terse, but its brevity is not effective—it omits essential information. While there is no verbosity, the minimalism undermines usefulness, making it insufficiently informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool lacks any context: no explanation of input/output, use cases, or relationship to other tools. Given the complexity implied by the parameters and sibling tools, this description is grossly incomplete.

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

Parameters2/5

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

The schema provides descriptions for maxId and sinceId, but userId, proxyUrl, resFormat, and screenName are undocumented. The description adds no further clarification, leaving parameter semantics partially unclear.

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

Purpose1/5

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

The description is essentially a placeholder, only providing a URL and metadata (Group: Tweets, Billing) without explicitly stating what the tool does. Even though the tool name suggests retrieving favorites, the description itself fails to convey any functional purpose.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool, how it fits into workflows, or alternatives. The description offers no context for choosing this over sibling tools.

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

All x-twitter 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