walkie-mcp

Fetch one recorded meeting (ChatGPT name)

fetch

Read-onlyIdempotent

Same read as get_meeting: one meeting's notes, action items, participants, and speaker-labeled transcript with timestamp links where recorded, paged for long meetings — the end of text says how to get the next page (pass its cursor). Cite the closest timestamp for exact quotes and decisions. Exists because ChatGPT's connector surface requires a tool named fetch; other clients should call get_meeting.

Use with an id from search. Do not use to find a meeting by topic (search / search_meetings).

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

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": "fetch"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Meeting id from search, 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.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description does not need to repeat that. It does add real behavior the annotations cannot express: transcripts are paged, the next-page instruction lives at the end of `text`, and unknown ids return an error. The "does not create, edit, or delete" line restates the destructiveHint annotation rather than adding to it.

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 payload-defining sentence comes first, followed by paging, citation guidance, the naming rationale, and then usage constraints. Dense but well ordered. The one meta sentence about ChatGPT's connector surface earns its place as routing guidance, though it is the most expendable line.

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 carries the return-value burden and does so: it names every returned component and explains how to continue past the first page. Combined with the error behavior and citation advice, nothing needed to call this correctly is missing.

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 the schema already documents all four parameters; baseline would be 3. The description goes slightly further by explaining the paging loop (pass the cursor, the end of `text` tells you how) and tying `cursor` to search hits opening at the matched transcript position, which clarifies how the parameters interact across calls.

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?

A specific verb and resource (read one recorded meeting) plus an enumeration of the returned content: notes, action items, participants, speaker-labeled transcript with timestamp links. It explicitly distinguishes itself from get_meeting ("same read as get_meeting") and from the search siblings, so an agent can place it immediately.

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 positive usage ("Use with an id from search"), a negative case with the correct alternative ("Do not use to find a meeting by topic (search / search_meetings)"), and a client-based routing rule (other clients should call get_meeting). Both when and when-not are stated with alternatives named.

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.