Skip to main content
Glama
getxapi

getxapi-mcp

Official

get_home_timeline

Read-only

Fetch your Twitter home timeline with two feed options: algorithmic recommendations or reverse-chronological following feed.

Instructions

Fetch your Twitter home timeline feed via API. Default is the 'For You' feed (algorithmic, includes recommended posts from accounts you don't follow); set following=true for the 'Following' feed (reverse-chronological, only accounts you follow).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNo
followingNofalse (default) = For You feed (includes recommendations); true = Following feed (only accounts you follow, reverse-chronological).
Behavior4/5

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

The description adds transparency about algorithmic vs reverse-chronological behavior and default feed selection, which goes beyond the readOnlyHint annotation.

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?

Two sentences efficiently convey the purpose, modes, and how to switch, with no unnecessary words.

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?

Given no output schema, the description does not cover return format, but the tool is simple and the behavioral context is adequate for an agent to use it correctly.

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

Parameters4/5

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

The description clarifies the default value and effect of the 'following' parameter, adding meaning beyond the schema description. The cursor parameter is not explained, but schema coverage is 50% and the description partially compensates.

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 clearly states it fetches the Twitter home timeline, and distinguishes between the 'For You' and 'Following' feeds with specific details about content sources and ordering.

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

Usage Guidelines4/5

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

The description explains when to use each mode (For You vs Following) but does not explicitly compare against sibling tools or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/getxapi/getxapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server