Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Follow a hashtag

follow_hashtag
Idempotent

Follow a hashtag to add all public posts carrying it to your home timeline, building a custom feed on Mastodon.

Instructions

Follow a hashtag, so every public post carrying it appears in your home timeline. The main way to build a feed on Mastodon.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hashtag": "<hashtag>"
    },
    "name": "follow_hashtag"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
hashtagYesWith or without the leading #.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, idempotent write, and the description adds the meaningful effect on the home timeline. It does not cover auth requirements or any side-effect caveats, but the annotation context lowers the burden on the description.

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 tight sentences, front-loaded with the action and its effect. There is no filler, no repetition of schema details, and every sentence earns its place.

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 simple mutation with one required parameter, complete schema descriptions, and rich annotations, the description is sufficient for an agent to invoke the tool correctly. It does not describe the response shape, but there is no output schema and that is not needed to decide to call it.

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?

Input schema coverage is 100%, and the schema already documents account resolution and that the hashtag may include a leading #. The description adds no parameter-level meaning beyond what the schema provides, so the baseline applies.

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?

States an explicit action and its consequence: following a hashtag routes every public post carrying it into the home timeline. It also positions the tool as 'the main way to build a feed on Mastodon,' distinguishing it from read-only alternatives like get_hashtag_timeline and from unfollow_hashtag.

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?

Gives a clear use case ('the main way to build a feed on Mastodon') plus a concrete behavioral effect, so an agent can tell when following a hashtag is the right operation. It does not explicitly discuss when to use a hashtag timeline or unfollow instead, but the context is unambiguous enough.

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