Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List who an account follows

get_following
Read-onlyIdempotent

Fetch the list of accounts a specific Mastodon user follows, with automatic pagination for large lists.

Instructions

Accounts a given account follows. Pages automatically.

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": {
      "acct": "<acct>"
    },
    "name": "get_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
acctYes
limitNoHow many. Pages automatically. Default 40.
max_idNoContinue from a previous page.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds 'Pages automatically,' a useful behavioral detail beyond the annotations' readOnly/openWorld/idempotent hints. It does not contradict annotations, and for a simple read-only listing tool the pagination note provides meaningful transparency.

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 short sentences with no filler; the core behavior is stated first and the pagination behavior follows. The description is efficiently sized for a simple list tool.

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 list operation, the description, schema, and annotations together cover the essential behavior, parameters, and safety profile. The lack of an output schema is acceptable because the return type ('accounts') is implied.

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 coverage is 75%: limit, max_id, and account already have descriptions. The phrase 'given account' clarifies that acct is the target account, but the description does not add format or default details beyond the schema. This meets the baseline for high schema coverage.

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 names the resource ('accounts a given account follows') and the title supplies the verb 'List', making the purpose clear. It is distinguishable from the sibling get_followers because it targets accounts the given account follows rather than followers.

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?

'Accounts a given account follows' implies the tool is for retrieving another account's follow list, but it gives no explicit guidance about when to prefer it over alternatives like get_followers or get_suggested_follows. 'Pages automatically' hints at handling paginated results but not when or how to request subsequent pages.

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