Skip to main content
Glama
tldv-public

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

Official
by tldv-public

get-meeting-metadata

Retrieve meeting details including name, date, organizer, and participants by providing a meeting ID from Zoom, Google Meet, or Microsoft Teams.

Instructions

Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metadata, including the name, the date, the organizer, participants and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for the 'get-meeting-metadata' tool. It takes a meeting ID, fetches the meeting data using TldvApi, and returns it as a JSON string in the required MCP response format.
    async ({ id }) => {
      const meeting = await tldvApi.getMeeting(id);
      return {
        content: [{ type: "text", text: JSON.stringify(meeting) }]
      };
    }
  • src/index.ts:58-68 (registration)
    Registers the 'get-meeting-metadata' tool with the MCP server using server.tool(), specifying name, description, input schema, and the handler function.
    server.tool(
      tools["get-meeting-metadata"].name,
      tools["get-meeting-metadata"].description,
      tools["get-meeting-metadata"].inputSchema.shape,
      async ({ id }) => {
        const meeting = await tldvApi.getMeeting(id);
        return {
          content: [{ type: "text", text: JSON.stringify(meeting) }]
        };
      }
    );
  • Tool declaration including name, description, and input schema (zod schema: object with 'id' as string). Used for capabilities and registration.
    "get-meeting-metadata": {
      name: "get-meeting-metadata",
      description: "Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metadata, including the name, the date, the organizer, participants and more.",
      inputSchema: z.object({ id: z.string() }),
    },
  • TldvApi.getMeeting helper method called by the tool handler. Makes an authenticated API request to TLDV's /meetings/{id} endpoint to retrieve meeting metadata.
    async getMeeting(meetingId: string): Promise<TldvResponse<Meeting>> {
      return this.request<Meeting>(`/meetings/${meetingId}`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates this is a read operation ('Get'), it doesn't disclose important behavioral traits like authentication requirements, rate limits, error conditions, or whether the meeting ID must be in a specific format. The description provides basic functional information but lacks operational context.

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 three sentences that each serve a purpose: stating the action, explaining the parameter, and describing the return value. It's front-loaded with the core functionality and avoids unnecessary elaboration while covering essential information.

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

Completeness3/5

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

For a single-parameter read tool with no annotations and no output schema, the description provides basic functional coverage but lacks important contextual details. It explains what the tool does and what it returns at a high level, but doesn't address authentication, error handling, or provide examples of the metadata structure that will be returned.

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 schema has 0% description coverage for its single parameter 'id'. The description adds some semantic context by stating 'The meeting ID is a unique identifier for a meeting', which provides meaning beyond the bare schema. However, it doesn't specify format requirements, examples, or constraints, leaving significant gaps in parameter understanding.

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 tool's purpose: 'Get a meeting by its ID' and specifies it returns meeting metadata including name, date, organizer, and participants. It uses specific verbs ('Get', 'return') and identifies the resource ('meeting'), but doesn't explicitly differentiate from sibling tools like 'list-meetings' or 'get-transcript'.

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 'list-meetings' or 'get-transcript'. It mentions the meeting ID is required but doesn't explain when this tool is appropriate compared to other meeting-related tools available on the server.

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