Skip to main content
Glama

Delete a hosted interview

talkform.delete_handoff
DestructiveIdempotent

Permanently deletes stored configuration and answers for an authorized project or OAuth account. Requires user confirmation and handoffs:delete permission.

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": "talkform.delete_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real value beyond them: it names exactly what is destroyed (stored configuration and answers), states the deletion is permanent, and lists the required permission and user-confirmation step. It stops short of saying whether the operation can be undone or what a successful response looks like.

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 permanence and scope of destruction are front-loaded before the permission/confirmation requirement. Every clause carries information an agent needs.

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 single-parameter destructive delete with no output schema, the description covers permanence, blast radius, permission, and confirmation, which is nearly everything needed. The remaining gap is the meaning of the 'id' argument, which neither schema nor description explains.

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?

Schema description coverage is 0%, and the description says nothing about the single required 'id' parameter — not what entity it identifies (a handoff/interview) nor that it must be a UUID. The only hint is 'authorized project or OAuth account', which describes scope, not the parameter.

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 (permanently deletes) and a concrete resource scope (stored configuration and answers for an authorized project or OAuth account), which clearly separates it from read siblings like get_handoff. It never uses the tool's own 'handoff' or 'interview' terminology, so an agent must infer that the target is a hosted interview.

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

Usage Guidelines3/5

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

The description gives prerequisites (user confirmation, handoffs:delete permission) but no guidance on when to choose this over adjacent mutations such as delete_webhook, nor any explicit when-not-to-use condition. Usage is implied by the destructive nature rather than stated.

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.