Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a list

delete_list
Destructive

Delete a Mastodon list without removing its member accounts. Requires explicit confirmation before execution.

Instructions

Delete a list. The accounts on it are not affected, only the list. Needs confirm: true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
accountNoWhich connected account to act as. Matches a full handle (alice@example.social), a bare username (alice), or an instance (example.social). Defaults to the first connected account. Call list_accounts to see them.
confirmNoMust be true for this to run. The result is public immediately or cannot be undone, so it is refused without an explicit confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds useful side-effect context beyond that: accounts on the list are not affected. It also states the confirm requirement, reinforcing that this is a destructive action requiring explicit confirmation.

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?

Three short sentences, each earning its place: the action, the side-effect scope, and the confirmation requirement. No filler or redundant elaboration.

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?

For a simple delete operation, the description plus rich schema and annotations cover everything needed to call it correctly: what is deleted, what is not affected, and that confirm must be true. The absence of an output schema is not a meaningful gap for agent invocation here.

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?

The input schema documents account and confirm thoroughly, and the tool description mentions 'Needs confirm: true.' The id parameter is not described in the schema, but its meaning as the list identifier is obvious from the tool name and description. Schema coverage is 67%, so this modest description meets the baseline without adding much new parameter detail.

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 states a specific verb and resource ('Delete a list') and immediately clarifies scope: 'The accounts on it are not affected, only the list.' This distinguishes it clearly from sibling tools like remove_from_list, which remove an account from a list rather than deleting the list itself.

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 gives clear context for when this tool applies: deleting an entire list while leaving its member accounts untouched. It does not explicitly name alternatives or say 'use remove_from_list instead', but the exclusion of account effects makes the intended usage clear enough.

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

Deploy Server

Other Tools