Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Delete a saved list

argorant_delete_list
DestructiveIdempotent

Delete a saved list or saved search for good. Use it only when the user wants the whole list gone; to take some people out use argorant_remove_list_items instead. Exports already made from it and people already in campaigns stay. It cannot be undone, so ask the user for explicit approval first and set confirmed=true only with that yes. It is free. More in the docs at https://docs.argorant.com/docs/agents/tools#lists

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": "argorant_delete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesThe list to delete, from argorant_list_lists.
confirmedNotrue only after the user's explicit yes to deleting this list

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds real behavioral context beyond them: the deletion is irreversible, exports already produced and people already in campaigns survive, and the confirmed=true flag must only follow an explicit yes. It even notes there is no credit cost, which matters for a paid platform.

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?

The destructive consequence and the confirmation requirement are front-loaded, and every sentence carries information an agent needs. The docs URL and 'It is free' are minor additions that slightly dilute an otherwise tight definition.

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 destructive two-parameter tool with full schema coverage, an output schema, and complete annotations, nothing an agent needs is missing. Irreversibility, side-effect scope, approval protocol, and the sibling alternative are all covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the workflow contract behind confirmed=true — approval must precede the call, not accompany it. It does not add further detail on list_id beyond the schema's pointer to argorant_list_lists, keeping it just short of a 5.

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?

States a specific verb and resource ('Delete a saved list or saved search') and covers both variants (list vs. saved search). It immediately distinguishes itself from the sibling argorant_remove_list_items by contrasting full-list deletion with partial removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the condition that selects this tool ('only when the user wants the whole list gone') and routes to the correct alternative ('to take some people out use argorant_remove_list_items instead'). It also states the precondition of explicit user approval before calling.

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

All Argorant toolsInspect
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.

Resources