Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Search Messages

search_messages
Read-onlyIdempotent

Search Google Chat messages by text or time range across spaces. Restrict to a specific space and control result limits to find what you need.

Instructions

Searches for messages in Google Chat spaces by text content and/or time range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional text to search for. If omitted, only time_filter is applied.
space_idNoOptional space to restrict the search to.
page_sizeNoMaximum number of messages to return per space.
max_spacesNoMaximum number of spaces to search when space_id is not provided (default 10).
time_filterNoOptional filter using Chat API createTime syntax. Examples: 'createTime > "2026-03-18T00:00:00-03:00"' 'createTime > "2026-03-18T00:00:00-03:00" AND createTime < "2026-03-19T00:00:00-03:00"'
user_google_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_spaces
      Added value: +{
+  "default": 10,
+  "description": "Maximum number of spaces to search when space_id is not provided (default 10).",
+  "type": "integer"
+}
    • addedInput schema / properties / page_size / description
      Added value: +"Maximum number of messages to return per space."
    • removedInput schema / properties / page_size / title
      Removed value: -"Page Size"
    • addedInput schema / properties / query / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / query / default
      Added value: +null
    • addedInput schema / properties / query / description
      Added value: +"Optional text to search for. If omitted, only time_filter is applied."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / query / type
      Removed value: -"string"
    • removedInput schema / properties / service
      Removed value: -{
-  "title": "service",
-  "type": "string"
-}
    • addedInput schema / properties / space_id / description
      Added value: +"Optional space to restrict the search to."
    • removedInput schema / properties / space_id / title
      Removed value: -"Space Id"
    • addedInput schema / properties / time_filter
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional filter using Chat API createTime syntax.\n         Examples:\n           'createTime > \"2026-03-18T00:00:00-03:00\"'\n           'createTime > \"2026-03-18T00:00:00-03:00\" AND createTime < \"2026-03-19T00:00:00-03:00\"'"
+}
    • removedInput schema / properties / user_google_email / title
      Removed value: -"User Google Email"
    • changedInput schema / required
      Previous value: -[
-  "service",
-  "user_google_email",
-  "query"
-]New value: +[
+  "user_google_email"
+]
    • removedInput schema / title
      Removed value: -"search_messagesArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the read-only, idempotent, non-destructive nature of the tool. The description adds that it searches by text/time and across spaces, which is useful, but it does not disclose additional behavioral details like pagination, rate limits, or multi-space scoping beyond what the schema already indicates. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence: 'Searches for messages in Google Chat spaces by text content and/or time range.' It is front-loaded with the verb and resource, contains no filler or redundant phrases, and every word contributes to understanding the tool's core purpose.

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 the presence of a rich output schema, detailed parameter descriptions, and annotations, the description is adequate for an agent to select and invoke the tool. It captures the essential search capability and differentiates from siblings, though it does not explicitly mention cross-space search or pagination—details available in the schema. The overall package is fairly complete.

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 83%, so parameters are well-documented (e.g., query optional, time_filter syntax, max_spaces defaults). The description adds a high-level mapping of 'text content' to query and 'time range' to time_filter, which is helpful but does not add new meaning beyond the existing schema documentation. The baseline is 3 due to high schema 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: 'Searches for messages in Google Chat spaces by text content and/or time range.' It specifies the resource (messages in Google Chat spaces) and the two search dimensions (text content, time range), distinguishing it from Gmail search and other message-related tools like get_messages.

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 for when to use this tool: searching for Chat messages by content or time. However, it does not explicitly mention alternatives or exclusion scenarios (e.g., 'use get_messages to fetch a specific thread' or 'use search_gmail_messages for email'). The context is clear but lacks explicit when-not-to-use guidance.

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/taylorwilsdon/google_workspace_mcp'

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