Skip to main content
Glama
MDBList MCP Server

MDBList MCP Server

by j1lt3d

Delete list

delete_list
DestructiveIdempotent

Permanently deletes a user-owned static MDBList list by ID; dynamic, official, and external lists cannot be deleted.

Instructions

Permanently delete one of the user's static lists (dynamic, official and external lists cannot be deleted).

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": {
      "list_id": "<list_id>"
    },
    "name": "delete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesMDBList list ID of one of your own lists (from get_user_lists). Never an external_id from browse_lists source 'external'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / list_id / description
      Previous value: -"Numeric MDBList list ID"New value: +"MDBList list ID of one of your own lists (from get_user_lists). Never an external_id from browse_lists source 'external'."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried structurally. The description still adds real value by emphasizing permanence and by restricting eligibility to the user's own static lists, which the annotations do not convey. It does not say whether contained items are also removed, a minor remaining gap.

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 with the destructive verb and the eligibility restriction front-loaded; no filler and nothing to trim.

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

Completeness4/5

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

For a one-parameter destructive tool with full annotation coverage and no output schema, this is nearly complete: it conveys permanence, scope, and exclusions. Only the side effects on list contents are left unstated.

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%, and the schema itself already warns that list_id must be an own-list ID from get_user_lists and never an external_id. The description's "static lists" phrasing corroborates that constraint but adds no new syntax or format detail, so baseline 3 applies.

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 and resource ("Permanently delete ... static lists") and narrows the target set by excluding dynamic, official, and external lists. An agent can tell this is the deletion counterpart to create_list/add_list_items without opening the schema, though no sibling tool is named explicitly.

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?

Gives a clear when-not condition: dynamic, official, and external lists cannot be deleted, which prevents the most likely misuse. It stops short of naming the alternative (e.g. use remove_list_items or search_lists to locate a deletable list), so it falls short of full when/when-not/alternatives coverage.

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