Skip to main content
Glama

get_timeline

Retrieve posts from your Bluesky home timeline using optional algorithms, pagination, and result limits to view social content.

Instructions

Get posts from your home timeline.

Args:
    ctx: MCP context
    algorithm: Optional algorithm to use for timeline
    cursor: Optional pagination cursor
    limit: Maximum number of results to return

Returns:
    Timeline feed with posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
algorithmNo
cursorNo
limitNo

Implementation Reference

  • The handler function for the 'get_timeline' tool. It uses the authenticated Bluesky client to fetch the home timeline with optional algorithm, cursor, and limit parameters, returning the timeline data or an error.
    @mcp.tool()
    def get_timeline(
        ctx: Context,
        algorithm: Optional[str] = None,
        cursor: Optional[str] = None,
        limit: Optional[int] = None,
    ) -> Dict:
        """Get posts from your home timeline.
    
        Args:
            ctx: MCP context
            algorithm: Optional algorithm to use for timeline
            cursor: Optional pagination cursor
            limit: Maximum number of results to return
    
        Returns:
            Timeline feed with posts
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            timeline_response = bluesky_client.get_timeline(algorithm, cursor, limit)
    
            # Convert the response to a dictionary
            if hasattr(timeline_response, "model_dump"):
                timeline_data = timeline_response.model_dump()
            else:
                timeline_data = timeline_response
    
            return {"status": "success", "timeline": timeline_data}
        except Exception as e:
            error_msg = f"Failed to get timeline: {str(e)}"
            return {"status": "error", "message": error_msg}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pagination via 'cursor' and result limiting via 'limit', which is helpful, but doesn't cover important aspects like authentication requirements, rate limits, error conditions, or what constitutes 'your home timeline' (e.g., authenticated user's timeline). The return format is minimally described as 'Timeline feed with posts' without detail.

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 efficiently structured with a clear purpose statement followed by organized sections for Args and Returns. Every sentence earns its place, with no redundant information. The formatting makes it easy to scan and understand quickly.

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

Completeness3/5

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

For a 3-parameter tool with no annotations and no output schema, the description provides basic but incomplete coverage. It explains parameters well and states the return type, but lacks details about authentication, error handling, rate limits, and the structure of the returned feed. Given the complexity of timeline operations, more behavioral context would be beneficial.

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 explicitly lists all three parameters with brief explanations, adding meaningful context beyond the schema's 0% description coverage. It clarifies that 'algorithm' is optional and for timeline selection, 'cursor' is for pagination, and 'limit' controls maximum results. This adequately compensates for the schema's lack of parameter descriptions.

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?

The description clearly states the action ('Get posts') and resource ('from your home timeline'), making the purpose immediately understandable. It distinguishes this from siblings like get_author_feed or get_post by specifying the home timeline context, though it doesn't explicitly contrast with all similar tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like get_author_feed, get_posts, or get_post_thread. It mentions 'your home timeline' which implies personal content, but offers no explicit when/when-not instructions or comparisons to sibling tools.

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/gwbischof/bluesky-social-mcp'

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