Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Get Notetaker Meetings

get_notetaker_meetings
Read-onlyIdempotent

Retrieve notetaker meetings with optional details including summaries, topics, action items, and transcripts. Filter by access level, search, or specific IDs.

Instructions

Retrieve notetaker meetings with optional detailed fields. Use include_summary, include_topics, include_action_items, and include_transcript flags to control which details are returned. Use access to filter by meeting access level (OWN, SHARED_WITH_ME, SHARED_WITH_ACCOUNT, ALL). Defaults to OWN. Supports filtering by ids, search term, and cursor-based pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by specific meeting IDs. Use this to fetch one or more specific meetings in a single call.
accessNoFilter meetings by access level. OWN: meetings the user participated in or invited the bot to. SHARED_WITH_ME: meetings shared with the user or their team. SHARED_WITH_ACCOUNT: meetings shared with the entire account. ALL: all meetings the user has access to.OWN
limitNoMaximum number of notetaker meetings to return per page (1-100).
cursorNoCursor for pagination. Use cursor from the previous page_info to fetch the next page.
searchNoSearch notetaker meetings by title, participant name, or email.
include_summaryNoWhether to include the AI-generated summary for each meeting.
include_topicsNoWhether to include discussion topics and talking points for each meeting.
include_action_itemsNoWhether to include action items for each meeting.
include_transcriptNoWhether to include the full transcript for each meeting. Transcripts can be very large.
Behavior4/5

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description adds behavioral context such as the large size of transcripts and pagination support, enhancing transparency without contradicting annotations.

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 concise, front-loads the purpose, and efficiently covers all key parameters in two sentences without redundancy.

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

Completeness4/5

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

Given 9 parameters, no output schema, and high schema coverage, the description adequately covers pagination, defaults, and parameter usage. It lacks return format details but that's acceptable without output schema.

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% with detailed parameter descriptions. The description adds value by grouping flags and explaining how to use them together (e.g., controlling details), and clarifying access level defaults.

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 clearly specifies the verb 'Retrieve' and the resource 'notetaker meetings' with optional detailed fields. It distinguishes itself from sibling tools by focusing on notetaker meetings, which is a specific domain not covered by other tools.

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 description provides clear context on filtering by access, IDs, search, and pagination, and defaults to OWN. It doesn't explicitly state when not to use or alternatives, but the context is sufficient given no direct sibling for this resource.

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/mondaycom/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server