Skip to main content
Glama

Delete a call's record

delete_call
Destructive

Delete the transcript, summary and recording of one call, for good (a deletion request from the person called, or your team's retention policy). The call row, its outcome and its cost remain. Reps can delete their own calls; managers and admins any.

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_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCall id or SID from list_calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description goes well beyond that by enumerating exactly which artifacts are destroyed and which survive, and by flagging permanence ('for good'). It also discloses the permission model, which is behavior an agent cannot infer from the schema or annotations.

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 sentences, no filler. The destruction scope is front-loaded and the permission caveat follows as a compact clause.

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 one-parameter tool with no output schema, the description supplies everything an agent needs to decide and act: what disappears, what persists, irreversibility, and authorization scope.

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 single `id` parameter is documented with its accepted forms and a pointer to list_calls. The description adds no further syntax or format detail, which is the expected baseline when the schema carries the parameter burden.

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 (delete) and precisely scopes the resource: the transcript, summary and recording of one call. It also explicitly names what is NOT removed (the call row, outcome, cost), which distinguishes it from any general call-mutation sibling.

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 concrete triggering conditions — a deletion request from the person called, or a team retention policy — plus who is authorized (reps for own calls, managers/admins for any). It stops short of naming an alternative sibling or an explicit 'do not use for X' exclusion, so it's clear context rather than full routing guidance.

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.