Skip to main content
Glama

search_meetings

Search meetings using natural language queries on titles, content, or participants. Retrieve meeting transcripts, notes, and summaries with speaker identification to quickly locate relevant discussions.

Instructions

Search meetings by title, content, or participants

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for meetings
limitNoMaximum number of results

Implementation Reference

  • The main handler function _search_meetings that executes the search logic: iterates meetings, scores them by matching query against title, participants, and transcript content, then returns formatted results.
    async def _search_meetings(self, query: str, limit: int = 10) -> List[TextContent]:
        """Search meetings by query."""
        if not self.cache_data:
            return [TextContent(type="text", text="No meeting data available")]
        
        query_lower = query.lower()
        results = []
        
        for meeting_id, meeting in self.cache_data.meetings.items():
            score = 0
            
            # Search in title
            if query_lower in meeting.title.lower():
                score += 2
            
            # Search in participants
            for participant in meeting.participants:
                if query_lower in participant.lower():
                    score += 1
            
            # Search in transcript content if available
            if meeting_id in self.cache_data.transcripts:
                transcript = self.cache_data.transcripts[meeting_id]
                if query_lower in transcript.content.lower():
                    score += 1
            
            if score > 0:
                results.append((score, meeting))
        
        # Sort by relevance and limit results
        results.sort(key=lambda x: x[0], reverse=True)
        results = results[:limit]
        
        if not results:
            return [TextContent(type="text", text=f"No meetings found matching '{query}'")]
        
        output_lines = [f"Found {len(results)} meeting(s) matching '{query}':\n"]
        
        for score, meeting in results:
            output_lines.append(f"• **{meeting.title}** ({meeting.id})")
            output_lines.append(f"  Date: {self._format_local_time(meeting.date)}")
            if meeting.participants:
                output_lines.append(f"  Participants: {', '.join(meeting.participants)}")
            output_lines.append("")
        
        return [TextContent(type="text", text="\n".join(output_lines))]
  • The tool registration with input schema defining parameters: query (required string) and limit (optional integer, default 10).
        name="search_meetings",
        description="Search meetings by title, content, or participants",
        inputSchema={
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "Search query for meetings"
                },
                "limit": {
                    "type": "integer", 
                    "description": "Maximum number of results",
                    "default": 10
                }
            },
            "required": ["query"]
        }
    ),
  • The call_tool dispatcher that routes 'search_meetings' tool calls to the _search_meetings handler method.
    if name == "search_meetings":
        return await self._search_meetings(
            query=arguments["query"],
            limit=arguments.get("limit", 10)
        )
Behavior3/5

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

With no annotations, the description must convey behavioral traits. It states the search fields but omits key behaviors: whether the tool returns full meeting details or summaries, whether it supports pagination, or if it is read-only. The limit parameter hints at maximum results, but the return format is not described.

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 a single sentence of seven words, which is highly concise. It front-loads the main action and is efficiently structured. However, it could include a brief mention of the return type without significantly increasing length.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description is incomplete. It does not explain what the search returns (e.g., a list of meeting summaries with IDs), nor does it mention how the limit parameter is applied. Sibling tools are not referenced to guide the agent's flow.

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 input schema already documents both parameters ('Search query for meetings' and 'Maximum number of results'). The description adds no extra meaning beyond the schema, meeting the baseline for full coverage.

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 states the tool's function as searching meetings and specifies the searchable fields (title, content, or participants). This distinguishes it from sibling tools like get_meeting_details (for a single meeting) or get_meeting_documents (for attachments), making the purpose unambiguous.

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

Usage Guidelines3/5

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

No explicit guidance is given on when to use this tool versus siblings. The description implies usage for search scenarios but lacks instructions on prerequisites, fallbacks, or alternative tools. For example, it does not mention that search results can be used to obtain meeting IDs for subsequent detail lookups.

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/maxgerlach1/granola-ai-mcp-server'

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