Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read your home timeline

get_home_timeline
Read-onlyIdempotent

Retrieve statuses from followed accounts and hashtags, newest first. Use since_hours for a time window or limit to control count.

Instructions

Statuses from the accounts and hashtags you follow, newest first. Pass since_hours to read a time window rather than a fixed count.

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

NameRequiredDescriptionDefault
limitNoHow many statuses. Pages automatically past the 40-per-request ceiling. Default 40.
max_idNoContinue from a previous page: pass the next_max_id from the last result.
accountNoWhich connected account to act as. Matches a full handle (alice@example.social), a bare username (alice), or an instance (example.social). Defaults to the first connected account. Call list_accounts to see them.
since_hoursNoInstead of a fixed count, return everything from the last N hours, up to `limit`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral details beyond that: newest-first ordering, the feed scope, and the since_hours time-window mode versus fixed-count mode.

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 concise sentences lead with the core purpose and then add the one non-obvious usage nuance. There is no filler or redundancy.

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

Completeness5/5

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

For a read-only timeline retrieval tool, the description plus fully covered schema provides all needed semantics: feed scope, ordering, pagination parameters, account selection, and the special time-window behavior. No output schema is needed because the return type is implied by 'statuses'.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents limit, max_id, account, and since_hours. The description adds only a slight rephrasing of since_hours as a time-window alternative, providing minimal extra value.

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 states a specific operation and resource: reading statuses from accounts and hashtags you follow, ordered newest first. This clearly distinguishes the home timeline from siblings like get_local_timeline, get_federated_timeline, and get_hashtag_timeline.

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 phrase 'accounts and hashtags you follow' gives clear context that this is the personalized home feed rather than public or list-based timelines. However, it does not explicitly name alternative tools or state when-not-to-use it.

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

Deploy Server

Other Tools