MeetNotes

Transcribe an attached audio file

meetnotes_import_audio

DestructiveIdempotent

Use this when the user attaches an audio recording — a meeting, call, interview, lecture or voice note — and wants it transcribed or turned into meeting notes or minutes of meeting (MoM). MeetNotes returns a speaker-labelled transcript plus minutes: summary, key points, decisions and action items with owners. Handles over 100 languages and mixed-language speech such as Hindi with English (Hinglish). Returns a job receipt with a job_id at once; processing continues on the server and spends the connected account's minutes. The same file twice returns the same meeting with deduplicated true and is never processed or charged again. Audio files only, within the upload size limit.

Input Schema

TableJSON Schema

Name	Required	Description
`file`	Yes	The attachment, exactly as the host supplies it.
`title`	No	Meeting title; when omitted the minutes name it.
`language_hints`	No	Up to 5 BCP-47 tags of languages likely spoken, most likely first.
`output_language`	No	The language the user is writing in; the minutes are written in it. A BCP-47 tag or a plain language name.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`kind`	Yes
`job_id`	Yes
`status`	Yes
`meeting_id`	Yes
`deduplicated`	Yes
`estimated_ready_at`	No	Roughly when a job still processing will be ready (ISO 8601); null when it cannot be estimated. Tell the user instead of polling.
`estimated_minutes_left`	No
`minutes_will_be_emailed`	No	True when MeetNotes will email the minutes to the user once ready, so they need not wait in the chat.
`next_poll_after_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 4, 2026

addedOutput schema / properties / estimated_minutes_left

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / estimated_ready_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Roughly when a job still processing will be ready (ISO 8601); null when it cannot be estimated. Tell the user instead of polling."
+}

addedOutput schema / properties / minutes_will_be_emailed

Added value: +{
+  "description": "True when MeetNotes will email the minutes to the user once ready, so they need not wait in the chat.",
+  "type": "boolean"
+}

First observedSep 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses asynchronous behaviour (immediate job receipt with job_id, processing continues server-side), a cost consequence (spends the connected account's minutes), idempotency mechanics with the deduplicated flag and no re-charge, and an input restriction (audio only, size limit). These are exactly the traits an agent needs and none are derivable from the structured fields.

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 usage trigger, then behaviour, cost and constraints in dense declarative sentences with no filler. It is a single long paragraph, but nearly every clause earns its place; only the language-coverage sentence borders on marketing.

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?

Given a nested-object schema and an output schema that covers return values, the description supplies everything else: async contract, cost, dedupe, and input limits. Nothing an agent needs in order to invoke it correctly is missing.

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?

Schema description coverage is 100%, so the schema already documents file, title, language_hints and output_language. The description adds only indirect colour (100+ languages, mixed-language Hinglish) without clarifying tag format or the file object. Baseline 3 applies when the schema carries the semantics.

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+resource ('transcribe an attached audio file') and enumerates the concrete inputs it covers (meeting, call, interview, lecture, voice note). It clearly separates this from siblings that fetch or list existing meetings by framing it as the entry point for a newly attached file.

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

Usage Guidelines4/5

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

The trigger condition is explicit and rich — 'when the user attaches an audio recording and wants it transcribed or turned into meeting notes.' It does not, however, name the sibling alternatives an agent should pick instead when the recording already exists in MeetNotes (e.g. meetnotes_list_recordings or meetnotes_get_transcript), nor state when-not-to-use.

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

All MeetNotes 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.

Resources

Need Help?