Skip to main content
Glama

List Transcripts

list_transcripts
Read-only

View all your transcription jobs on GhostMinutes. Retrieve a list of submitted transcription requests.

Instructions

List your transcription jobs on GhostMinutes (authenticated accounts only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function (async callback) that requires auth, calls client.listTranscripts(), and returns the result as text and structured content.
      async () => {
        requireAuth(client);
        const body = await client.listTranscripts();
        return {
          content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
          structuredContent: jsonStructured(body),
        };
      },
    );
  • Input schema definition for list_transcripts — takes no input (z.object({})), with title, description, and annotations.
    {
      title: 'List Transcripts',
      description:
        'List your transcription jobs on GhostMinutes (authenticated accounts only).',
      inputSchema: z.object({}),
      annotations: { readOnlyHint: true, openWorldHint: false },
    },
  • The register() function that registers the tool named 'list_transcripts' on the MCP server.
    export function register(server: McpServer, client: GhostMinutesClient): void {
      server.registerTool(
        'list_transcripts',
        {
          title: 'List Transcripts',
          description:
            'List your transcription jobs on GhostMinutes (authenticated accounts only).',
          inputSchema: z.object({}),
          annotations: { readOnlyHint: true, openWorldHint: false },
        },
        async () => {
          requireAuth(client);
          const body = await client.listTranscripts();
          return {
            content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
            structuredContent: jsonStructured(body),
          };
        },
      );
    }
  • src/server.ts:35-35 (registration)
    Invocation of registerListTranscripts(server, client) in server.ts to wire up the tool.
    registerListTranscripts(server, client);
  • Client helper method listTranscripts() that sends a GET request to /mcp/jobs with Bearer auth and ensures OK response.
    async listTranscripts(): Promise<unknown> {
      try {
        const res = await this.http.get('/mcp/jobs', {
          headers: { Authorization: `Bearer ${this.apiKey}` },
        });
        return this.ensureOk(res);
      } catch (e) {
        this.handleThrown(e);
      }
    }
Behavior4/5

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

Annotations already mark it as read-only (readOnlyHint=true). The description adds a critical behavioral constraint: 'authenticated accounts only'. No contradictions with annotations. Additional context about listing scope is provided.

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, front-loaded sentence that conveys the essential purpose and constraint. Every word earns its place; there is no fluff or redundancy.

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 parameterless list operation with clear annotations, the description is complete. It includes authentication context, and the absence of output schema is acceptable for a simple listing tool. No additional information is necessary.

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

Parameters4/5

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

The input schema has zero parameters, so schema coverage is 100% trivially. According to rules, baseline for 0 parameters is 4. No parameter information is needed, and the description does not add any, which is appropriate.

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 clearly states the verb 'list', the resource 'transcription jobs', and the context 'on GhostMinutes (authenticated accounts only)'. This differentiates it from sibling tools like 'get_transcript' (single) and 'delete_transcript'.

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 implies usage context by noting authentication requirement, but does not provide explicit guidance on when to use this tool versus alternatives like 'get_transcript' or 'delete_transcript'. No when-not-to-use or alternative names mentioned.

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