Skip to main content
Glama

Delete a search

deleteRoleSearch
DestructiveIdempotent

Delete a Search, the people it found and the network and outside searches it started. Only whoever started it or a team owner can delete it, and it can't be undone. Name the Search to the user and get a yes before calling.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "roleSearchId": "<roleSearchId>"
    },
    "name": "deleteRoleSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
roleSearchIdYes

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description still adds meaningful context: exactly what else is destroyed downstream, that the action is irreversible, what permission is needed, and that the tool's inputs and results are logged. That logging disclosure is a behavioral fact found nowhere in the structured fields.

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 scope and the confirmation requirement are front-loaded in a tight opening paragraph, which is exactly the right ordering for a high-risk call. The trailing data-logging sentence is boilerplate that sits slightly apart from the operational content, but it is short and clearly separable.

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 single-item delete with two parameters and an output schema, everything an agent needs is present: what is removed, who may remove it, that it is permanent, and that user confirmation is required first. Return values need not be described because an output schema exists.

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

Parameters2/5

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

With schema coverage at 50%, the description carries partial burden, yet it never mentions either parameter. orgId is documented in-schema as the multi-org selector, but roleSearchId — the single required parameter — has only a uuid format and no description anywhere, and the description does not say what it identifies or where to obtain it.

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 Search') and immediately defines the blast radius: the people it found plus the network and outside searches it started. That cascade detail distinguishes it from the sibling delete tools (deleteResume, deleteApplication) which operate on single artifacts.

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 the authorization condition (creator or team owner) and an explicit procedural prerequisite ('Name the Search to the user and get a yes before calling'), which is strong pre-invocation guidance. It does not name a sibling alternative, but no alternative deletion path for role searches is evident from the definition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources