grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.messagePins.list

Lists pinned messages in a Google Chat space so users can retrieve important conversations for easy access, with pagination support.

Instructions

Lists message pins in a space. Users can pin important messages in spaces for easy access. For more information, see Pin or unpin a conversation in Google Chat. Requires user authentication with one of the following authorization scopes: - https://www.googleapis.com/auth/chat.spaces.pins.readonly - https://www.googleapis.com/auth/chat.spaces.pins - https://www.googleapis.co [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the paramsmap), or read whole frombody_file` Siblings over the same resource: create, delete.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`parent`	Yes	[URL path segment] Required. The parent space which owns the collection of pinned items Format: `spaces/{space}`
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of message pins returned. The service might return fewer messages than this value. The maximum value is 100. If you use a value mor
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Optional. A page token received from a previous list message pins call. Provide this parameter to retrieve the subsequent page. When paginating, all other param

Output Schema

Name	Required	Description	Default
`messagePins`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of message pins returned. The service might return fewer messages than this value. The maximum value is 100. If you use a value mor"New value: +"[query parameter] Optional. The maximum number of message pins returned. The service might return fewer messages than this value. The maximum value is 100. If you use a value mor"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"Optional. A page token received from a previous list message pins call. Provide this parameter to retrieve the subsequent page. When paginating, all other param"New value: +"[query parameter] Optional. A page token received from a previous list message pins call. Provide this parameter to retrieve the subsequent page. When paginating, all other param"

changedInput schema / properties / parent / description

Previous value: -"Required. The parent space which owns the collection of pinned items Format: `spaces/{space}`"New value: +"[URL path segment] Required. The parent space which owns the collection of pinned items Format: `spaces/{space}`"

addedInput schema / properties / parent / pattern
```
Added value: +"^spaces/[^/]+$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "messagePins": {
+      "items": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries full burden and does disclose meaningful behavior: it requires user authentication with specific authorization scopes, is an HTTP GET, and returns the resource as JSON. The generic 'request bodies are built from typed parameters / body_file' sentence is boilerplate that fits awkwardly for a GET list, slightly undercutting clarity.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, which is good. However, the trailing HTTP GET / body-building boilerplate is templated filler that doesn't earn its place for a list operation, detracting from an otherwise tight description.

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?

An output schema exists, so return values needn't be explained, and all 7 parameters are fully described in the schema. Auth and scope requirements are surfaced in the description, making it largely complete for a list operation; only explicit pagination/usage guidance is missing.

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 schema already documents parent, pageSize, and pageToken. The description adds no parameter-specific meaning beyond generic boilerplate about typed params winning over the params map, so it provides no value beyond the schema.

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 opening sentence 'Lists message pins in a space' gives a clear verb (Lists), a specific resource (message pins), and scope. It also names the resource siblings (create, delete), so an agent can orient it against the related operations without opening a schema.

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?

The description implies this is the read/list operation and mentions siblings 'create, delete', but it never states conditions for choosing this over those alternatives. Usage is only inferable from the verb, not explicitly guided.

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

Deploy Server