Loom Transcript MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getLoomTranscriptC | Get transcript text from a Loom video URL |
| getLoomCommentsC | Get comments from a Loom video URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves comments and the other retrieves transcript text from a Loom video URL. There is no overlap or ambiguity between them, as they target different data types from the same resource.
Both tools follow a consistent verb_noun pattern with 'get' as the verb and descriptive nouns ('LoomComments', 'LoomTranscript'). The naming is uniform and predictable across the tool set.
With only 2 tools, the server feels thin for a transcript-focused domain, lacking operations like search, update, delete, or other common transcript management functions. This minimal set may limit agent capabilities for comprehensive workflows.
The tool set is severely incomplete for a transcript domain, offering only retrieval functions without create, update, delete, or search capabilities. This creates significant gaps that could lead to agent failures when trying to perform full lifecycle operations.