Skip to main content
Glama

search_meetings

Search across meeting titles, summaries, and transcripts by keywords or exact phrases to find relevant passages with snippets and timestamps.

Instructions

Word search across meeting titles, summaries, and transcripts. Meetings with every query word (any order, case- and accent-insensitive) come first, then partial matches; rare words weigh more, exact-phrase hits lead, and ties keep recency. Words of up to three letters or digits match only whole words. Wrap the query in double quotes for an exact phrase. Hits carry kind, snippet, and timestamp; one meeting gives at most five transcript hits.

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": {
      "query": "<query>"
    },
    "name": "search_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum hits (default 50).
queryYesText to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses ranking order (all-words matches first, then partials), weighting of rare words, exact-phrase precedence, recency tie-breaking, the short-token whole-word rule, and the five-transcript-hits-per-meeting cap. It also names the return fields (kind, snippet, timestamp), so result shape is predictable before calling.

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 core operation, then ranking behavior, then tokenization rules, then return shape – a logical progression with no filler. The middle sentence is long and clause-dense, which slightly taxes scanning but every clause conveys distinct behavior.

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?

There is no output schema, and the description compensates by naming the hit fields and the per-meeting transcript cap. Gaps: no mention of whether results can be paged beyond limit (no offset exists), and no statement of the corpus boundary (own meetings vs. all workspace meetings), which matters for a search tool with no annotations.

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 baseline is 3, but the description goes beyond the schema by explaining query semantics: case- and accent-insensitivity, word order independence, the three-character whole-word rule, and double-quote phrasing. The limit parameter is left entirely to the schema, which is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'Word search across meeting titles, summaries, and transcripts.' An agent immediately knows what is searched and what corpus is covered. It does not name a sibling to distinguish itself from search_files/search_agent_notes, which keeps it at 4 rather than 5.

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?

Usage is implied by the resource (find meetings by text) and the description adds useful query-construction guidance such as quoting for exact phrases. However, it never states when to prefer this over list_meetings or search_agent_notes, nor any exclusion or prerequisite, so tool selection is left to inference.

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