twikit-mcp

get_home_timeline

Fetch the authenticated user's home timeline, choosing from 'for_you' or 'following' feeds.

Instructions

Get the authenticated user's home timeline ('for_you' or 'following').

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_home_timeline"
  }
}

Input Schema

Name	Required	Default
`kind`	No	for_you
`count`	No
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 5, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the action and the kind values, but doesn't mention pagination behavior (cursor), count limits, rate limits, or what the response contains. This is a minimal statement that leaves the agent without key behavioral context.

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?

The description is a single sentence that immediately identifies the action and resource, with no filler or unnecessary detail. It is optimally concise and front-loaded.

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

Completeness2/5

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

Given the tool's simplicity, the description covers the core purpose but omits any information about return format (no output schema), pagination with cursor, or behavioral constraints. The absence of annotations and output schema places greater responsibility on the description, which it does not fully meet.

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 coverage for parameters is 0%, and the description only restates the enum values for 'kind' without explaining count or cursor. The schema itself provides defaults and types, but the description does not add practical guidance on parameter usage, such as how cursor controls pagination.

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 the tool retrieves the authenticated user's home timeline, with the specific kind values enumerated. This verb+resource phrasing distinguishes it from related tools like get_user_tweets or 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 Guidelines3/5

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

The description implies usage for the current user's home feed, but doesn't explicitly state when to prefer this over alternatives. The 'authenticated user' phrasing provides some differentiation, but no direct exclusions or alternative recommendations are given.

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