Skip to main content
Glama
tldv-public

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

Official
by tldv-public

list-meetings

Retrieve and filter your recorded meetings from Zoom, Google Meet, and MS Teams by date, status, or participation to find specific sessions quickly.

Instructions

List all meetings based on the filters provided. You can filter by date, status, and more. Those meetings are the sames you have access to in the TLDV app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
pageNo
limitNo
fromNo
toNo
onlyParticipatedNo
meetingTypeNo

Implementation Reference

  • The MCP tool handler registration for 'list-meetings'. This is the function that executes when the tool is called, fetching meetings via TldvApi and returning the JSON-stringified result.
    server.tool(
      tools["list-meetings"].name,
      tools["list-meetings"].description,
      tools["list-meetings"].inputSchema.shape,
      async (input) => {
        const meetings = await tldvApi.getMeetings(input);
        return {
          content: [{ type: "text", text: JSON.stringify(meetings) }]
        };
      }
    );
  • Zod schema defining the input parameters for the list-meetings tool (GetMeetingsParamsSchema), used for validation.
    export const GetMeetingsParamsSchema = z.object({
      query: z.string().optional(), // search query
      page: z.number().int().positive().optional(), // page number      
      limit: z.number().int().positive().optional().default(50), // number of results per page
      from: z.string().datetime().optional(), // start date
      to: z.string().datetime().optional(), // end date
      onlyParticipated: z.boolean().optional(), // only return meetings where the user participated
    
      // meeting type. internal is default. 
      // This is used to filter meetings by type. Type is determined by comparing the organizer's email with the invitees' emails. 
      // If the organizer's domain is different from at least one of the invitees' domains, the meeting is external.
      // Otherwise, the meeting is internal.  
      meetingType: z.enum(['internal', 'external']).optional(), 
    });
  • src/index.ts:30-34 (registration)
    Tool definition object for 'list-meetings' used in MCP server capabilities declaration.
    "list-meetings": {
      name: "list-meetings",
      description: "List all meetings based on the filters provided. You can filter by date, status, and more. Those meetings are the sames you have access to in the TLDV app.",
      inputSchema: GetMeetingsParamsSchema,
    },
  • TldvApi.getMeetings method: validates input, constructs query parameters, and makes the API request to fetch meetings list.
    async getMeetings(params: GetMeetingsParams = {}): Promise<TldvResponse<GetMeetingsResponse>> {
      const validatedParams = GetMeetingsParamsSchema.parse(params);
      const queryParams = new URLSearchParams();
      
      if (validatedParams.query) queryParams.append('query', validatedParams.query);
      if (validatedParams.page) queryParams.append('page', validatedParams.page.toString());
      if (validatedParams.limit) queryParams.append('limit', validatedParams.limit.toString());
      if (validatedParams.from) queryParams.append('from', validatedParams.from);
      if (validatedParams.to) queryParams.append('to', validatedParams.to);
      if (validatedParams.onlyParticipated !== undefined) queryParams.append('onlyParticipated', validatedParams.onlyParticipated.toString());
      if (validatedParams.meetingType) queryParams.append('meetingType', validatedParams.meetingType);
    
      return this.request<GetMeetingsResponse>(`/meetings?${queryParams}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions filtering capability and TLDV app access, but fails to describe pagination behavior (implied by 'page' and 'limit' parameters), rate limits, authentication requirements, or what 'status' filtering entails. For a 7-parameter tool with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately concise with two sentences. The first sentence front-loads the core functionality (listing with filters), and the second adds context about access. No wasted words, though the TLDV app reference 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?

For a 7-parameter tool with no annotations and no output schema, the description is incomplete. It doesn't explain return values, pagination behavior, error conditions, or detailed parameter usage. The TLDV app reference is insufficient context. Given the complexity and lack of structured data, the description should provide more operational guidance.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions filtering by 'date, status, and more' which partially maps to 'from', 'to', and possibly 'meetingType' parameters, but doesn't explain the 'query' parameter, 'onlyParticipated', pagination parameters, or the meaning of 'status' versus 'meetingType'. With 7 undocumented parameters, the description adds minimal semantic value.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('meetings'), and specifies filtering capability. It distinguishes from siblings like 'get-highlights' or 'get-transcript' by focusing on listing meetings rather than retrieving specific content. However, it doesn't explicitly differentiate from 'get-meeting-metadata' which might have overlapping functionality.

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 mentions filtering by date, status, and more, but provides no guidance on when to use this tool versus sibling tools like 'get-meeting-metadata'. It doesn't specify prerequisites, alternatives, or exclusions. The TLDV app reference is vague and doesn't help the agent understand usage 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/tldv-public/tldv-mcp-server'

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