mastodon-mcp-server

Account Update

account_update

Idempotent

Update the authenticated Mastodon account profile by changing display name, bio, bot status, or follow-request approval settings.

Instructions

Update the authenticated account's profile.

Input Schema

TableJSON Schema

Name	Required	Description
`bot`	No	Mark account as a bot (True/False).
`note`	No	New bio/note (profile description).
`locked`	No	Require approval for follow requests (True/False).
`display_name`	No	New display name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv1.0.5Sep 12, 2026

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

addedInput schema / properties / bot / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / bot / default
```
Added value: +null
```
removedInput schema / properties / bot / type
```
Removed value: -"boolean"
```

addedInput schema / properties / display_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / display_name / default
```
Added value: +null
```
removedInput schema / properties / display_name / type
```
Removed value: -"string"
```

addedInput schema / properties / locked / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / locked / default
```
Added value: +null
```
removedInput schema / properties / locked / type
```
Removed value: -"boolean"
```

addedInput schema / properties / note / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / note / default
```
Added value: +null
```
removedInput schema / properties / note / type
```
Removed value: -"string"
```

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the one thing annotations cannot: the target is strictly the authenticated account, not an arbitrary user. It still omits partial-update semantics (do omitted/null fields leave values unchanged?) and any rate-limit or auth-scope detail.

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?

A single front-loaded sentence with zero padding, which is efficient. It is arguably too terse to be maximally useful, but no sentence is wasted.

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

Completeness3/5

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

Complexity is low (a four-field, all-optional update), an output schema exists, and annotations carry the safety profile, so the terse description is close to sufficient. What is missing is the key operational fact that this is a partial merge update where omitted fields are left unchanged, plus any permission context — a gap an agent could trip over.

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 all four parameters (bot, note, locked, display_name) are already documented in the schema. The description only gestures at 'profile', which arguably covers note and display_name but not bot or locked, and adds no format or defaulting guidance. Baseline 3 is appropriate.

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?

States a specific verb (Update) and resource (the authenticated account's profile), which is unambiguous. It does not, however, differentiate itself from siblings like account_get or account_verify, so an agent gets no routing help from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives (e.g., other account_* tools), and no prerequisites such as authentication requirements or what happens if no fields are supplied. The agent must infer everything from the name.

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

Deploy Server