grr

Overview Schema Source Related Servers Discussions Admin

chat.users.sections.items.list

List the spaces contained in a Google Chat section for the authenticated user. Supports pagination and filtering by space to retrieve section items.

Instructions

Lists items in a section. Only spaces can be section items. For details, see Create and organize sections in Google Chat. Requires user authentication with the authorization scope: - https://www.googleapis.com/auth/chat.users.sections - https://www.googleapis.com/auth/chat.users.sections.readonly [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: move.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`filter`	No	[query parameter] Optional. A query filter. Currently only supports filtering by space. For example, `space = spaces/{space}`. Invalid queries are rejected with an `INVALID_ARGUM
`params`	No	Parameter map merged into the request; typed parameters win.
`parent`	Yes	[URL path segment] Required. The parent, which is the section resource name that owns this collection of section items. Only supports listing section items for the calling user. W
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of section items to return. The service may return fewer than this value. If unspecified, at most 10 section items will be returned
`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 section items call. Provide this to retrieve the subsequent page. When paginating, all other parameters pr

Output Schema

Name	Required	Description	Default
`sectionItems`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 26, 2026

changedInput schema / properties / filter / description

Previous value: -"Optional. A query filter. Currently only supports filtering by space. For example, `space = spaces/{space}`. Invalid queries are rejected with an `INVALID_ARGUM"New value: +"[query parameter] Optional. A query filter. Currently only supports filtering by space. For example, `space = spaces/{space}`. Invalid queries are rejected with an `INVALID_ARGUM"

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of section items to return. The service may return fewer than this value. If unspecified, at most 10 section items will be returned"New value: +"[query parameter] Optional. The maximum number of section items to return. The service may return fewer than this value. If unspecified, at most 10 section items will be returned"

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

changedInput schema / properties / pageToken / description

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

changedInput schema / properties / parent / description

Previous value: -"Required. The parent, which is the section resource name that owns this collection of section items. Only supports listing section items for the calling user. W"New value: +"[URL path segment] Required. The parent, which is the section resource name that owns this collection of section items. Only supports listing section items for the calling user. W"

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

changedOutput schema / (root)

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

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the burden and does disclose the auth requirement and both scopes plus HTTP GET, which implies a read operation. However, pagination behavior and the boilerplate about body_file/params maps are generic and not tailored to a GET listing operation.

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?

The core purpose is front-loaded well, but the trailing boilerplate about request bodies, typed flags, body_file, and params maps is largely irrelevant for a GET and dilutes the useful content.

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, auth is covered, and all 8 params are documented in the schema. The description is complete enough for an agent to call it correctly, with only minor behavioral detail 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 parameters are already fully documented, giving a baseline of 3. The description only adds the constraint that only spaces can be section items, marginal extra meaning over the schema.

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 first sentence gives a clear verb+resource ('Lists items in a section') and specifies the constraint that only spaces can be section items. It names the sibling 'move' over the same resource, giving some distinction, though differentiation is light.

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 name and the 'only spaces can be section items' constraint, and it briefly points at the 'move' sibling. There is no explicit when-to-use versus alternatives or exclusions beyond that single reference.

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

Deploy Server