Skip to main content
Glama

list_meetings

Read-onlyIdempotent

Lists the analysed meetings the caller may see, as cards, newest first, with the filter choices the Meetings screen offers. Use it to show or search the meeting list, and to find a meetingId for Get Meeting, Get Meeting Transcript, Get Share Link or the notes routes (meetings[].id).

Any member of the company may call it, but what comes back depends on their role. An owner or admin sees every meeting in the company. A member sees only the meetings they booked or were invited to, plus every meeting of each team they are in (only their own when they are in no team). It never returns meetings from a company other than the one named in x-company-id.

Paging: send limit (1 to 100) to get pages. When there are more results, nextCursor holds a token; pass it back as cursor to get the next page. nextCursor is null on the last page. Without limit, every matching meeting comes back in one response. Never build a cursor yourself.

The first page (no cursor) also carries the extras: filters (the types, tags, people and teams that actually occur, each with a count), totals (all meetings the caller may see, and how many of them still need attention, ignoring the filters) and processing (up to 50 meetings the caller may see that are still being analysed, newest first). On later pages filters and totals are null and processing is empty, so keep the first page's copy. meetingCount is the number of matches across all pages. In filters.people, team is true for someone who was ever on the company's side of a call.

Filters combine: q searches title, headline, summary, type, tag, a participant's name or email, a team's name, or an exact meeting id; type, tag and person take values from filters; teamId limits to meetings booked by or with that team's members (an id from filters.teams[].value); within keeps meetings from the last N days; from and to pick a custom date range instead; status is open (still needs something) or handled.

Team filter: an owner or admin may pass any of the company's teams. A member may pass only a team they are in, and filters.teams lists only their teams.

A company with no meetings gets an empty list, not an error.

Errors: 400 VALIDATION_FAILED when a query value is out of range, a date cannot be read, or the cursor is not one this server issued; 401 when not signed in or the sign-in expired; 404 TEAM_NOT_FOUND when teamId is not one of this company's teams, or (for a member) not a team they are in. GET https://meet-analyzer-api.50agents.com/api/v1/ui/meetings?q=&type=&person=&tag=&teamId=&within=&from=&to=&status=&recorded=&cursor=&limit=

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional. Free-text search, up to 200 characters. Matches title, headline, summary, type, tag, a participant's name or email, a team's name, or an exact meeting id
toNoOptional. End of a custom date range, a date or date-time (ISO 8601), exclusive
tagNoOptional. A tag, a value from filters.tags[].value
fromNoOptional. Start of a custom date range, a date or date-time (ISO 8601), inclusive. Either end may be left open
typeNoOptional. Meeting type, a value from filters.types[].value, e.g. SALES, SUPPORT, PARTNERSHIP, MARKETING, INTERNAL
limitNoOptional. Page size, 1 to 100. Omit to get every matching meeting at once
cursorNoOptional. The nextCursor from the previous page. Omit for the first page
personNoOptional. A participant's name, a value from filters.people[].value
statusNoOptional. open (still needs something) or handled
teamIdNoOptional. A team id from filters.teams[].value. Keeps meetings that team's members booked or were invited to. A member may only pass a team they are in
withinNoOptional. Whole number 1 to 3650: only meetings that started within this many days
recordedNoOptional. mine returns only meetings the caller recorded on the Liliphant phone app (Add Phone Recording), newest first, still limited to what the caller may see. Used by the app's "Recorded on your phone" list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recorded
      Added value: +{
      +  "description": "Optional. mine returns only meetings the caller recorded on the Liliphant phone app (Add Phone Recording), newest first, still limited to what the caller may see. Used by the app's \"Recorded on your phone\" list",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Optional. Page size, 1 to 100. Omit to get every matching meeting at once. e.g. 20"New value: +"Optional. Page size, 1 to 100. Omit to get every matching meeting at once"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses role-dependent result visibility, strict company isolation, first-page-only extras, cursor behavior, team-filter permission constraints, and specific error conditions. This is substantial behavioral context for a complex read operation.

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 definition is front-loaded with purpose, visibility, and paging before moving into filters and errors. It is lengthy for a tool with 12 parameters, but most sentences carry useful operational detail; some repetition of schema parameter descriptions keeps it from being maximally concise.

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?

With no output schema, the description adequately explains the returned list shape, pagination fields, first-page extras, totals, processing list, and error behavior. Combined with the fully described input schema, it gives enough context to call the tool correctly.

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

Parameters4/5

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

Schema coverage is already 100%, so the schema carries most individual parameter documentation. The description adds meaningful relational semantics: filters combine, values come from filters.*, teamId is constrained by role, cursors must come from the server, and omitting limit returns all matches.

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?

The description states a specific verb and resource ('Lists the analysed meetings'), the return shape ('as cards, newest first'), and the caller's visibility scope. It also distinguishes this list/search operation from follow-on tools such as Get Meeting and Get Meeting Transcript.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool to show or search the meeting list and to find a meetingId for downstream routes. It also explains when role-based visibility applies, how filters combine, how paging works, and that an empty company returns an empty list rather than an error.

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