grr

Overview Schema Source Related Servers Discussions Admin

chat.users.sections.items.move

Moves a Google Chat section item, such as a space, from one section to another by specifying the target section.

Instructions

Moves an item from one section to another. For example, if a section contains spaces, this method can be used to move a space to a different section. 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 [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON MoveSectionItemRequest object accepting targetSection; pass it via params or whole via body_file Siblings over the same resource: list.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. The resource name of the section item to move. Format: `users/{user}/sections/{section}/items/{item}`
`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.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON MoveSectionItemRequest object.
`request_body`	No	Request body of type MoveSectionItemRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`sectionItem`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON MoveSectionItemRequest object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type MoveSectionItemRequest: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "targetSection": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Required. The resource name of the section item to move. Format: `users/{user}/sections/{section}/items/{item}`"New value: +"[URL path segment] Required. The resource name of the section item to move. Format: `users/{user}/sections/{section}/items/{item}`"

addedInput schema / properties / name / pattern

Added value: +"^users/[^/]+/sections/[^/]+/items/[^/]+$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "sectionItem": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "space": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that this is an HTTP POST mutation, that it requires user authentication with the chat.users.sections scope, and crucially that it is refused under --readonly safety profiles. It also states the return is the API response resource as JSON, so the agent knows the shape of the result.

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?

Purpose and example are front-loaded, followed by auth, safety and body details in a compact block. Slightly dense with linked references and redundant re-explanation of params/body_file, but every sentence still carries information.

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?

For a mutation tool with no annotations and an existing output schema, the description supplies the missing safety, auth and request-body context the schema cannot. It omits the resource-name format for the item being moved, though the schema covers that.

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 coverage is 100%, so the required `name` path format is already fully documented. The description adds only the request-body detail (MoveSectionItemRequest with targetSection, passable via params or body_file), which the schema descriptions also state, so the incremental value is small.

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?

Opens with a specific verb+resource: 'Moves an item from one section to another', and the space example grounds it in concrete Chat objects. It never names the closest sibling (chat.users.sections.position) or the listing sibling, so differentiation relies on the agent inferring it from the name.

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 'if a section contains spaces, move a space to a different section' example implies when this applies and the destination section is supplied via targetSection. There is no explicit when-not-to-use guidance and no pointer to chat.users.sections.position for reordering within a section, which is the most likely confusion.

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

Deploy Server