Skip to main content
Glama
tldv-public

tl;dv MCP for Zoom, Google Meet and MS Teams

Official
by tldv-public

get-highlights

Extract key moments from recorded meetings in Zoom, Google Meet, and MS Teams by providing a meeting ID to access important discussion points.

Instructions

Allows you to get highlights from a meeting by providing a meeting ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meetingIdYes

Implementation Reference

  • MCP server.tool registration which includes the handler function that executes the get-highlights tool logic by calling tldvApi.getHighlights and formatting the response.
    server.tool(
      tools["get-highlights"].name,
      tools["get-highlights"].description,
      tools["get-highlights"].inputSchema.shape,
      async ({ meetingId }) => {
        const highlights = await tldvApi.getHighlights(meetingId);
        return {
          content: [{ type: "text", text: JSON.stringify(highlights) }]
        };
      }
    );
  • Tool definition including input schema (z.object({ meetingId: z.string() })) for get-highlights.
    "get-highlights": {
      name: "get-highlights",
      description: "Allows you to get highlights from a meeting by providing a meeting ID.",
      inputSchema: z.object({ meetingId: z.string() }),
    },
  • Implementation of getHighlights in TldvApi class, which performs the HTTP request to fetch highlights.
    async getHighlights(meetingId: string): Promise<TldvResponse<GetHighlightsResponse>> {
      return this.request<GetHighlightsResponse>(`/meetings/${meetingId}/highlights`);
    }
  • Zod schema and type definition for the output response of get-highlights (GetHighlightsResponse).
    export const GetHighlightsResponseSchema = z.object({
      meetingId: z.string(),
      data: z.array(HighlightSchema),
    });
    
    export type GetHighlightsResponse = z.infer<typeof GetHighlightsResponseSchema>;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'get highlights' but doesn't specify what 'highlights' entail (e.g., key points, summaries, timestamps), whether this is a read-only operation, or any constraints like rate limits or authentication needs. The description is too vague to adequately inform behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a simple tool, though it could be more informative.

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

Completeness2/5

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

Given the tool's complexity (simple retrieval), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'highlights' are, how they're formatted, or any behavioral aspects, leaving significant gaps for an AI agent to understand the tool fully.

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?

The description mentions the parameter 'meetingId' implicitly ('by providing a meeting ID'), but with 0% schema description coverage, it doesn't add meaningful semantics beyond what the schema already indicates (a required string). Since there's only one parameter, the baseline is 4, but the description fails to explain what a 'meeting ID' is or where to find it, so it's scored lower.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('get highlights from a meeting') with a specific verb and resource, but it doesn't distinguish it from sibling tools like 'get-meeting-metadata' or 'get-transcript' which also retrieve meeting-related data. The purpose is clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-transcript' or 'get-meeting-metadata'. It only states what the tool does without indicating context, exclusions, or prerequisites for usage.

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/tldv-public/tldv-mcp-server'

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