walkie-mcp

Read one recorded meeting in full

get_meeting

Read-onlyIdempotent

Read one recorded meeting: AI notes, action items, participants, and the speaker-labeled transcript with timestamp links where recorded, all in text. Cite the closest timestamp for exact quotes and decisions. Long transcripts come back in pages; each page's transcript_page says which lines and minutes it covers, the meeting's total length, how many pages are left, and a next_cursor. To read the whole meeting, keep calling with the same id and cursor = next_cursor until transcript_page.complete is true — never treat one page as the full call. To read one stretch, pass start_minute and/or end_minute; a search hit's cursor opens the transcript at that hit. Notes come on the first page. Takes an id from search_meetings or list_meetings.

Use when you already have a meeting id and need the notes or quotes. Do not use to find a meeting by topic (search_meetings) or to page the archive (list_meetings). ChatGPT clients call the same read as fetch.

Does not create, edit, or delete meetings. Unknown ids return an error, not an empty meeting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`id`	Yes	Meeting id from search_meetings or list_meetings, e.g. "mtg-1786560198190".
`cursor`	No	Continue reading: pass the previous page's next_cursor unchanged. A search hit's cursor works too and opens the transcript at that hit.
`end_minute`	No	Stop before this minute (e.g. 122). With start_minute, reads one stretch of a long meeting; it still pages if the stretch is long.
`start_minute`	No	Start the transcript at this minute of the meeting (e.g. 60). Ignored when cursor is set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continue reading: pass the previous page's next_cursor unchanged. A search hit's cursor works too and opens the transcript at that hit.",
+  "type": "string"
+}

addedInput schema / properties / end_minute

Added value: +{
+  "description": "Stop before this minute (e.g. 122). With start_minute, reads one stretch of a long meeting; it still pages if the stretch is long.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / start_minute

Added value: +{
+  "description": "Start the transcript at this minute of the meeting (e.g. 60). Ignored when cursor is set.",
+  "minimum": 0,
+  "type": "number"
+}

First observedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds substantial behavior the annotations cannot convey: paginated transcripts, the transcript_page metadata fields, the next_cursor loop and the warning not to treat one page as the full call, notes appearing only on the first page, ignored start_minute when cursor is set, and errors rather than empty results for unknown ids. It also states the non-mutation guarantee explicitly, matching the annotations rather than contradicting them.

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?

Front-loaded with the resource and payload, then pagination, then when-to-use/exclusions. Dense and nearly waste-free, though the pagination paragraph is long and the 'never treat one page as the full call' warning restates the transcript_page.complete instruction already given.

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?

No output schema exists, so the description carries the return-shape burden and does so thoroughly: the `text` field, transcript_page contents (line/minute coverage, total length, pages remaining, next_cursor, complete), and where notes appear. Combined with pagination and error semantics, an agent can call and consume this tool correctly end to end.

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 100%, so baseline is 3; the description goes beyond it by explaining the pagination protocol (same id, cursor = next_cursor until transcript_page.complete), the start_minute/end_minute range-read pattern, and the precedence rule that a search hit's cursor opens at that hit. Minor residual gap: it does not clarify units or clamping for end_minute beyond the minute-based examples already in the schema.

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?

States a specific verb and resource ('Read one recorded meeting') and enumerates what comes back: AI notes, action items, participants, speaker-labeled transcript with timestamp links. It explicitly names the two siblings it is not (search_meetings for topic lookup, list_meetings for archive paging), so an agent can route without opening any schema.

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?

Gives both sides of the decision: 'Use when you already have a meeting id and need the notes or quotes' plus explicit 'Do not use to find a meeting by topic (search_meetings) or to page the archive (list_meetings).' It also states the id source (search_meetings or list_meetings) and explains how a search hit's cursor is reused, closing the loop between search and read.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All walkie-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.