account_unfollow
Unfollow a specific account on Mastodon by providing its numeric account ID.
Instructions
Unfollow an account.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | Yes | Numeric account ID to unfollow. |
Unfollow a specific account on Mastodon by providing its numeric account ID.
Unfollow an account.
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | Yes | Numeric account ID to unfollow. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits such as side effects, prerequisites, or results of unfollowing a non-followed account.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler, but it is slightly too brief for a tool with no annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description lacks details on success behavior, error cases, or preconditions, making it insufficient for complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes the parameter fully (numeric account ID to unfollow). The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (unfollow) and the resource (account), distinguishing it from related tools like account_follow and account_block.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like account_unblock or account_mute; usage is only implied by the verb.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VitexSoftware/mastodon-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server