Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Get Messages

get_messages
Read-onlyIdempotent

Retrieve Google Chat messages from a space, filterable by creation time or thread, with configurable sort order and page size.

Instructions

Retrieves messages from a Google Chat space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_byNocreateTime desc
space_idYes
page_sizeNo
message_filterNoOptional 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_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed10 schema fields changedv1.0.1
    • 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
+}
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, but the description adds no behavioral context beyond the basic retrieval action. It does not mention filtering, ordering, pagination, or any limits, nor does it 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.

Conciseness5/5

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

The description is a single, efficient sentence with no filler or repetition. It front-loads the verb and object.

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 tool with 5 parameters and a sibling search_messages, this description is too sparse to support selection and correct invocation. The presence of an output schema helps with return values, but the description fails to explain filtering capabilities, pagination defaults, or how this differs from related message retrieval tools.

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

Parameters2/5

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

Schema description coverage is only 20% (just message_filter has a description), yet the tool description adds no explanation for user_google_email, space_id, order_by, or page_size. The phrase 'from a Google Chat space' weakly maps to space_id but is not enough to compensate for the low coverage.

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 uses a specific verb ('Retrieves') and names a concrete resource ('Google Chat space'), making the core action clear. However, it does not distinguish this from sibling tools like 'search_messages' or 'search_drive_files', so it falls short of full differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as search_messages. The description is a single statement with no context, exclusions, or alternative references.

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