Skip to main content
Glama
Sign In

Getlead

by ad.getle
OverviewDiscussionsAdmin

Delete a lead list

delete_list
Destructive

Permanently delete a list and every lead in it. Irreversible: ask the user first, then call again with 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": {
      "list_id": "<list_id>"
    },
    "name": "delete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true once the user has agreed
list_idYesList id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the annotations by specifying permanence, that every lead is deleted, and that the operation is irreversible. It also clarifies the two-step confirmation flow, which is essential behavioral information not present in the annotations alone.

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?

Two short sentences contain all essential information, with the destructive action front-loaded and the safety workflow stated immediately after. Every sentence earns its place with no redundancy.

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 delete operation with two simple parameters and no output schema, the description covers what an agent needs: what is deleted, that it is irreversible, and how to invoke it safely with confirm true. Annotations reinforce the destructive and non-idempotent nature.

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. The description adds value by explaining the confirm parameter's role in the irreversible deletion flow, tying it to the user-approval requirement. list_id is adequately covered by 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 clearly states the action: permanently delete a list and every lead in it. It identifies both the resource and the destructive scope, distinguishing it from sibling tools that create, update, or export lists.

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 usage context by instructing the agent to ask the user first and then call again with confirm true. It does not explicitly name alternatives or exclusions, but the destructive nature and safety workflow are clearly communicated.

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

All Getlead 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