Mastodon

Get Account

get_account

Read-onlyIdempotent

Get a Mastodon account profile by ID (e.g., '109382839472938472'). Returns bio, follower/following counts, post history, and verification status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric Mastodon account ID (e.g. "109302436954721982")

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Account ID
`bot`	Yes	Whether account is a bot
`url`	Yes	Profile URL
`acct`	Yes	Full account address
`note`	Yes	Bio/note text
`avatar`	Yes	Avatar image URL
`username`	Yes	Username handle
`created_at`	Yes	Account creation timestamp
`display_name`	Yes	Display name
`statuses_count`	Yes	Number of posts
`followers_count`	Yes	Number of followers
`following_count`	Yes	Number following

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "acct": {
+      "description": "Full account address",
+      "type": "string"
+    },
+    "avatar": {
+      "description": "Avatar image URL",
+      "type": "string"
+    },
+    "bot": {
+      "description": "Whether account is a bot",
+      "type": "boolean"
+    },
+    "created_at": {
+      "description": "Account creation timestamp",
+      "type": "string"
+    },
+    "display_name": {
+      "description": "Display name",
+      "type": "string"
+    },
+    "followers_count": {
+      "description": "Number of followers",
+      "type": "number"
+    },
+    "following_count": {
+      "description": "Number following",
+      "type": "number"
+    },
+    "id": {
+      "description": "Account ID",
+      "type": "string"
+    },
+    "note": {
+      "description": "Bio/note text",
+      "type": "string"
+    },
+    "statuses_count": {
+      "description": "Number of posts",
+      "type": "number"
+    },
+    "url": {
+      "description": "Profile URL",
+      "type": "string"
+    },
+    "username": {
+      "description": "Username handle",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "username",
+    "acct",
+    "display_name",
+    "url",
+    "followers_count",
+    "following_count",
+    "statuses_count",
+    "created_at",
+    "bot",
+    "avatar",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "id": "109302436954721982"
+  }
+]
```
First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds what the output contains (bio, counts, etc.) but does not disclose additional behavioral traits beyond what annotations imply.

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?

A single sentence that efficiently captures the action, resource, input example, and output summary. No wasted words.

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

Completeness5/5

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

The description is complete for a simple tool with one parameter and an existing output schema. It mentions key return fields, making it sufficient for an agent to understand the tool's purpose.

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%; the schema already includes a clear description and example for the id parameter. The description's mention of 'by ID' adds no new semantic value beyond the schema.

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?

The description uses a specific verb 'Get' and resource 'Mastodon account profile', clearly indicating the input (ID) and output (bio, counts, post history, verification status). It distinguishes from all sibling tools, none of which are for account retrieval.

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?

The description implicitly states when to use (need account by ID) but does not explicitly mention when not to use or alternatives. However, given the tool's simplicity and lack of similar siblings, the guidance is still clear.

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

All Mastodon tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.