Skip to main content
Glama

Get transcript summary

get_transcript_summary
Read-onlyIdempotent

Returns the AI-generated summary of a completed recording: executive summary, key points, action items, and speaker profiles. Call it when the user wants the gist, decisions, or follow-ups from a recording without reading the full transcript. A summary is only generated when one was asked for, so a recording may not have one; the result says so when it does not.

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": "get_transcript_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecording id from list_transcripts

Output Schema

NameRequiredDescriptionDefault
existsYesFalse when no summary has been generated yet
contentNoLegacy full summary text
messageNoExplanation when no summary exists
createdAtNoWhen the summary was generated
keyPointsNoKey points discussed
actionItemsNoAction items identified
potentialIssuesNoRisks or issues raised
speakerProfilesNoPer-speaker profiles/contributions, when available
executiveSummaryNoHigh-level summary paragraph
keyRecommendationsNoRecommendations extracted from the discussion
importantInformationNoNotable facts, figures, and dates
prioritizedActionItemsNoAction items with owner/priority details, when available

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: summaries are only generated on request, so absence is a normal outcome and the response signals it. That pre-empts a common failure mode. It does not describe size limits or format of the summary.

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?

Three sentences, front-loaded with what is returned, then when to call, then the caveat. Every sentence carries distinct information with no repetition of the title or schema.

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 one-parameter read tool with a full output schema and complete annotations, the description covers purpose, trigger, and the not-found edge case. Nothing an agent needs in order to call it correctly is missing.

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 already documented as a recording id from list_transcripts. The description adds no additional meaning about the identifier, so baseline 3 applies.

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 and resource ('Returns the AI-generated summary of a completed recording') and enumerates the payload: executive summary, key points, action items, speaker profiles. This lets an agent distinguish it from get_transcript (full transcript) and list_transcripts without opening a schema.

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 a clear triggering condition: call it when the user wants 'the gist, decisions, or follow-ups ... without reading the full transcript.' The alternative (full transcript) is implied rather than named, so it stops just short of explicit sibling routing.

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.

Resources