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

Get Messages

get_messages

Read-onlyIdempotent

Fetch chat messages from a Google Chat space by providing user email and space ID. Optionally filter by creation time or thread to pinpoint specific conversations.

Instructions

Retrieves messages from a Google Chat space.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_by`	No		createTime desc
`space_id`	Yes
`page_size`	No
`message_filter`	No	Optional filter string using the Chat API filter syntax. Supports createTime and thread.name. 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"' 'thread.name = spaces/X/threads/Y'
`user_google_email`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / message_filter / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / message_filter / type
```
Added value: +"string"
```

Changed10 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / message_filter

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional filter string using the Chat API filter syntax.\n            Supports createTime and thread.name.\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\"'\n              'thread.name = spaces/X/threads/Y'"
+}

removedInput schema / properties / order_by / title
```
Removed value: -"Order By"
```
removedInput schema / properties / page_size / title
```
Removed value: -"Page Size"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

removedInput schema / properties / space_id / title
```
Removed value: -"Space Id"
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "space_id"
-]New value: +[
+  "user_google_email",
+  "space_id"
+]

removedInput schema / title
```
Removed value: -"get_messagesArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only the space-scope context and does not disclose pagination, filtering, ordering, or the role of user_google_email, but it does not contradict the 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 one direct sentence with no filler, and the main action is front-loaded. It is under-specified for the tool's complexity, but its structure is concise.

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?

For a 5-parameter tool with a required user_google_email and a sibling search_messages tool, this description is too thin. It lacks parameter semantics and usage guidance, though the output schema and annotations cover return values and safety.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at only 20%, the description needed to compensate for the undocumented parameters such as user_google_email, space_id, order_by, and page_size. It does not mention any of them and adds no meaning beyond the schema property names.

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?

The description states the operation (Retrieves messages) and the resource scope (from a Google Chat space), which separates it from the Gmail message tools. It does not explicitly distinguish it from the sibling search_messages tool, so it falls just short of a top score.

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

Usage Guidelines2/5

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

There is no guidance on when to use get_messages versus search_messages, nor any context about when this tool is the right choice. No preconditions, exclusions, or alternatives are mentioned.

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

Deploy Server