mastodon-mcp-server

Notifications Get

notifications_get

Read-onlyIdempotent

Retrieve notifications for the authenticated Mastodon account, optionally limiting results and excluding specific notification types.

Instructions

Get notifications for the authenticated account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of notifications (default 20, max 30).
`exclude_types`	No	Types to exclude: 'follow', 'favourite', 'reblog', 'mention', 'poll', 'follow_request', 'update', 'status'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.5Sep 12, 2026

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

addedInput schema / properties / exclude_types / anyOf

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

addedInput schema / properties / exclude_types / default
```
Added value: +null
```

changedInput schema / properties / exclude_types / description

Previous value: -"Types to exclude: 'follow', 'favourite', 'reblog',"New value: +"Types to exclude: 'follow', 'favourite', 'reblog',\n           'mention', 'poll', 'follow_request', 'update', 'status'."

removedInput schema / properties / exclude_types / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / exclude_types / type
```
Removed value: -"array"
```
addedInput schema / properties / limit / default
```
Added value: +20
```

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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no mention of pagination, ordering, or whether results are consumed/cleared after reading, which is the key behavioral question for a notifications endpoint.

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 no filler or redundancy. It is appropriately compact, though its brevity borders on under-specification rather than true economy.

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?

With rich annotations, a complete input schema, and an output schema present, the description needn't explain return values. For a simple two-parameter read tool this is minimally adequate, but the absence of any note about pagination limits or the relationship to notification_dismiss leaves a small gap.

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 100%; both limit (with default/max) and exclude_types (with the full enum of types) are fully documented in the schema, so the description need not repeat them. Baseline 3 applies since the description adds no extra parameter meaning.

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 clear verb (Get) and resource (notifications) scoped to the authenticated account, which is unambiguous on its own. It does not, however, distinguish itself from siblings like notification_dismiss or notifications_clear, though the verb difference makes the distinction reasonably inferable.

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?

The description gives no guidance on when to call this versus notification_dismiss or notifications_clear, nor any prerequisites such as authentication requirements. Usage must be inferred entirely 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