Skip to main content
Glama

Delete Transcript

delete_transcript

Remove a transcription job permanently using its job ID.

Instructions

Delete a transcription job from your GhostMinutes account (destructive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTranscription job id

Implementation Reference

  • The register function that creates and registers the 'delete_transcript' tool on the MCP server, including its handler logic
    export function register(server: McpServer, client: GhostMinutesClient): void {
      server.registerTool(
        'delete_transcript',
        {
          title: 'Delete Transcript',
          description:
            'Delete a transcription job from your GhostMinutes account (destructive).',
          inputSchema: z.object({
            id: z.string().min(1).describe('Transcription job id'),
          }),
          annotations: { readOnlyHint: false, openWorldHint: false },
        },
        async ({ id }) => {
          requireAuth(client);
          const body = await client.deleteTranscript(id);
          return {
            content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
            structuredContent: jsonStructured(body),
          };
        },
      );
    }
  • Input validation schema for 'delete_transcript' requiring an 'id' string parameter
    inputSchema: z.object({
      id: z.string().min(1).describe('Transcription job id'),
    }),
    annotations: { readOnlyHint: false, openWorldHint: false },
  • src/server.ts:37-37 (registration)
    Registration of delete_transcript tool in the main server file
    registerDeleteTranscript(server, client);
  • HTTP client method that sends a DELETE request to /mcp/jobs/:id with Bearer token auth
    async deleteTranscript(id: string): Promise<unknown> {
      try {
        const res = await this.http.delete(
          `/mcp/jobs/${encodeURIComponent(id)}`,
          {
            headers: { Authorization: `Bearer ${this.apiKey}` },
          },
        );
        return this.ensureOk(res);
      } catch (e) {
        this.handleThrown(e);
      }
    }
Behavior3/5

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

Annotations already indicate non-read-only (readOnlyHint=false). The description adds the explicit '(destructive)' label, which is helpful, but lacks details on irreversibility, permissions, or effects on related data.

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?

The description is a single concise sentence that immediately conveys the action and resource, with no superfluous words.

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 simple delete operation with one parameter and no output schema, the description adequately covers purpose and destructiveness. However, it omits mention of outcome (e.g., success response) or error cases, which would be helpful.

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 description coverage is 100% (the 'id' parameter is described as 'Transcription job id'). The tool description does not add any additional semantics beyond what the schema already provides.

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 explicitly states the action 'delete' and the resource 'transcription job', and distinguishes it from sibling tools like get_transcript or list_transcripts by noting destructiveness.

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

Usage Guidelines2/5

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

No guidance on when or why to use this tool beyond stating it deletes a job. Does not mention prerequisites, conditions, or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rocketech-Software-Development/ghostminutes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server