Skip to main content
Glama

Get Transcript

get_transcript
Read-only

Get the transcript of a meeting by its job ID. Use this to access saved transcriptions from your GhostMinutes account.

Instructions

Fetch a saved transcription job by id from your GhostMinutes account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTranscription job id

Implementation Reference

  • Registers the 'get_transcript' tool on the MCP server. The handler function requires auth, calls client.getTranscript(id), and returns the result as JSON text content with structured content.
    export function register(server: McpServer, client: GhostMinutesClient): void {
      server.registerTool(
        'get_transcript',
        {
          title: 'Get Transcript',
          description:
            'Fetch a saved transcription job by id from your GhostMinutes account.',
          inputSchema: z.object({
            id: z.string().min(1).describe('Transcription job id'),
          }),
          annotations: { readOnlyHint: true, openWorldHint: false },
        },
        async ({ id }) => {
          requireAuth(client);
          const body = await client.getTranscript(id);
          return {
            content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
            structuredContent: jsonStructured(body),
          };
        },
      );
    }
  • Input schema for the 'get_transcript' tool: requires a single 'id' string parameter (min length 1).
    inputSchema: z.object({
      id: z.string().min(1).describe('Transcription job id'),
    }),
  • src/server.ts:7-36 (registration)
    Import and registration of the get_transcript tool module. Line 7 imports it, line 18 lists it in EXPECTED_TOOL_NAMES, line 36 calls registerGetTranscript(server, client) during server creation.
    import { register as registerGetTranscript } from './tools/get-transcript.js';
    import { register as registerListTranscripts } from './tools/list-transcripts.js';
    import { register as registerSummarize } from './tools/summarize.js';
    import { register as registerTranscribeSync } from './tools/transcribe-url-sync.js';
    import { register as registerTranscribeUrl } from './tools/transcribe-url.js';
    
    export const EXPECTED_TOOL_NAMES = [
      'transcribe_audio_url',
      'transcribe_audio_url_sync',
      'get_transcription_status',
      'list_transcripts',
      'get_transcript',
      'delete_transcript',
      'summarize',
      'get_credits',
    ] as const;
    
    export type ExpectedToolName = (typeof EXPECTED_TOOL_NAMES)[number];
    
    export function createServer(client: GhostMinutesClient): McpServer {
      const server = new McpServer({
        name: 'ghostminutes-mcp',
        version: '0.1.0',
      });
    
      registerTranscribeUrl(server, client);
      registerTranscribeSync(server, client);
      registerGetStatus(server, client);
      registerListTranscripts(server, client);
      registerGetTranscript(server, client);
  • The client method getTranscript(id) that performs the HTTP GET request to /mcp/jobs/{id} with Bearer auth.
    async getTranscript(id: string): Promise<unknown> {
      try {
        const res = await this.http.get(
          `/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 read-only (readOnlyHint=true). Description adds nothing beyond, e.g., no mention of error behavior or required job state.

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?

One sentence, front-loaded with key information, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple fetch tool with one param and annotations, but lacks description of return content, which is useful since no output schema.

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%, so description need not add much. It repeats 'id' as 'Transcription job id', providing no additional semantics.

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?

Description clearly states verb 'fetch', resource 'transcription job', and scope 'by id from GhostMinutes account'. It distinguishes from siblings like 'delete_transcript' and 'list_transcripts'.

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?

No explicit when-to-use or alternatives. Implied by purpose, but lacks guidance on prerequisites or context.

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