Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

chat.users.sections.list

Lists a Chat user's sections to group conversations and customize spaces in navigation, with pagination support for retrieving all sections.

Instructions

Lists sections available to the Chat user. Sections help users group their conversations and customize the list of spaces displayed in Chat navigation panel. 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 [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, patch, position.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
parentYes[URL path segment] Required. The parent, which is the user resource name that owns this collection of sections. Only supports listing sections for the calling user. To refer to th
dry_runNoReturn the request that would be sent, without sending it.
pageSizeNo[query parameter] Optional. The maximum number of sections to return. The service may return fewer than this value. If unspecified, at most 10 sections will be returned. The maxi
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
pageTokenNo[query parameter] Optional. A page token, received from a previous list sections call. Provide this to retrieve the subsequent page. When paginating, all other parameters provide

Output Schema

NameRequiredDescriptionDefault
sectionsNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"Optional. The maximum number of sections to return. The service may return fewer than this value. If unspecified, at most 10 sections will be returned. The maxi"New value: +"[query parameter] Optional. The maximum number of sections to return. The service may return fewer than this value. If unspecified, at most 10 sections will be returned. The maxi"
    • addedInput schema / properties / pageSize / format
      Added value: +"int32"
    • changedInput schema / properties / pageToken / description
      Previous value: -"Optional. A page token, received from a previous list sections call. Provide this to retrieve the subsequent page. When paginating, all other parameters provide"New value: +"[query parameter] Optional. A page token, received from a previous list sections call. Provide this to retrieve the subsequent page. When paginating, all other parameters provide"
    • changedInput schema / properties / parent / description
      Previous value: -"Required. The parent, which is the user resource name that owns this collection of sections. Only supports listing sections for the calling user. To refer to th"New value: +"[URL path segment] Required. The parent, which is the user resource name that owns this collection of sections. Only supports listing sections for the calling user. To refer to th"
    • addedInput schema / properties / parent / pattern
      Added value: +"^users/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "nextPageToken": {
+      "type": "string"
+    },
+    "sections": {
+      "items": {
+        "properties": {
+          "displayName": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sortOrder": {
+            "type": "integer"
+          },
+          "type": {
+            "enum": [
+              "SECTION_TYPE_UNSPECIFIED",
+              "CUSTOM_SECTION",
+              "DEFAULT_DIRECT_MESSAGES",
+              "DEFAULT_SPACES",
+              "DEFAULT_APPS"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses required user authentication and specific authorization scopes, and notes the HTTP GET method (implying read-only). However, it does not cover rate limits, error behavior, or side effects, leaving some behavioral gaps.

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 mostly front-loaded with the core purpose and includes relevant context (definition of sections, auth scopes, siblings). However, the explanation of request body construction is tangential for a GET operation and the support link, while helpful, could be considered extraneous. Overall it is reasonably concise but could be tightened.

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 that an output schema exists and the input schema fully documents parameters (100% coverage), the description provides sufficient context for an agent to invoke the tool: it states the operation, required auth, HTTP method, and sibling alternatives. Minor gaps in usage guidance are tolerable given the schema richness.

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 fully documents all parameters. The description adds only meta-information about how request bodies are constructed (typed parameters vs. params map or body_file), which does not clarify the meaning of individual parameters. Baseline score of 3 is appropriate.

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 a specific verb (Lists) and resource (sections), along with scope (available to the Chat user). It also explicitly names the sibling operations (create, delete, patch, position) over the same resource, distinguishing this listing tool from them.

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 that this is the list operation and notes the existence of sibling operations, but does not explicitly state when to use this tool versus alternatives (e.g., 'use this to retrieve all sections; use create to make a new one'). No explicit when/when-not guidance is provided.

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

Deploy Server

Other Tools