mastodon-mcp-server

Account Relationships

account_relationships

Read-onlyIdempotent

Retrieve the authenticated user's relationship to one or more Mastodon accounts by providing numeric account IDs. Check following, blocking, muting, and other connection statuses.

Instructions

Get the authenticated user's relationship to one or more accounts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_ids`	Yes	List of numeric account IDs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.5Sep 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.1Jun 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare it as a safe read-only, idempotent operation. The description adds that it returns relationship data (which could include following, blocking, muting, etc.) but doesn't specify what fields are returned or the behavior for accounts that don't exist. Since annotations cover the safety profile and an output schema exists, this is adequate.

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?

Single concise sentence that front-loads the action and resource. No extraneous information, and the scope ('one or more') is stated efficiently.

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 operation with a single required parameter, comprehensive schema, annotations, and an output schema, the description is nearly sufficient. It could mention pagination or return format, but given the output schema exists, those details are available elsewhere.

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?

With one parameter and 100% schema description coverage, the schema fully documents account_ids as a list of numeric IDs. The description implies batch operations ('one or more accounts'), which adds context but doesn't specify whether it's limited to a maximum or how it handles invalid IDs. Baseline 4 applies since schema is comprehensive.

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 a specific verb (Get) and resource (relationship to accounts) with clear scope ('one or more'). Clearly distinguishes from siblings like account_followers (who follows an account) or account_search (finding accounts) since this returns the authenticated user's own relationship.

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 use case is implied by the description: retrieving relationship data for specific accounts the user already knows IDs for. However, it doesn't explicitly differentiate from similar tools like account_statuses or explain when to use this vs. other account methods beyond a general read operation.

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

Deploy Server