Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read your instance's local timeline

get_local_timeline
Read-onlyIdempotent

Fetch public statuses from your Mastodon instance, with pagination and time-based filtering to browse local posts.

Instructions

Everything public posted by accounts on your own instance. On a small themed instance this is the most useful timeline there is; on mastodon.social it is a firehose.

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_local_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

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false). The description adds behavioral context beyond those: content is public, scoped to the local instance, and can be a high-volume 'firehose' on large instances, which is useful for expecting large result sets.

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

Conciseness4/5

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

The description is only two sentences and front-loads the core definition. The second sentence adds useful usage context, though the subjective 'most useful timeline there is' is slightly less precise than a more objective condition would be.

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?

For a read-only timeline tool with robust annotations and fully documented parameters, the description plus input schema is sufficient. It establishes scope, content type, and scale. It doesn't explicitly describe the response shape, but the name and schema's pagination references make the return type reasonably clear.

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 every parameter already has a meaningful description. The tool description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate.

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 defines the resource and scope: 'Everything public posted by accounts on your own instance.' This distinguishes it from the federated timeline (other instances) and the home timeline (followed accounts), while the tool name and title provide the read/get verb.

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 gives useful context ('On a small themed instance this is the most useful timeline there is; on mastodon.social it is a firehose') that implies when it is appropriate, but it does not explicitly name alternatives like get_federated_timeline or get_home_timeline 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