Skip to main content
Glama

chat.users.sections.delete

Deletes a custom Chat section and moves any contained items, such as spaces, to default sections instead of deleting them.

Instructions

Deletes a section of type CUSTOM_SECTION. If the section contains items, such as spaces, the items are moved to Google Chat's default sections and are not deleted. 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 DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) 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: create, list, patch, position.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Required. The name of the section to delete. Format: `users/{user}/sections/{section}`
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The name of the section to delete. Format: `users/{user}/sections/{section}`"New value: +"[URL path segment] Required. The name of the section to delete. Format: `users/{user}/sections/{section}`"
    • addedInput schema / properties / name / pattern
      Added value: +"^users/[^/]+/sections/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that deletion is irreversible, that contained items are relocated to default sections rather than destroyed, required user auth and scope, refusal under readonly profiles, and the post-delete return shape. This is rich behavioral context beyond the name.

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?

Key facts (delete, item relocation) are front-loaded and the sentences mostly earn their place. The HTTP DELETE / readonly-profile boilerplate and return-body mechanics add some length that is only loosely tied to the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a delete tool with no annotations but an output schema, the description supplies the missing pieces an agent needs: irreversible side effects, item relocation, auth/scope requirements, and return behavior. Nothing essential is omitted.

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 all five parameters are already documented. The description adds only a minor note on how typed params override the `params` map and on `body_file` usage, which is marginal beyond the schema. Baseline 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?

States a specific verb+resource: 'Deletes a section of type `CUSTOM_SECTION`', and immediately clarifies the important caveat that contained items are moved, not deleted. The agent can tell exactly what this does without opening the 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 deletion and lists sibling operations (create, list, patch, position) at the end, but only as a bare list — it never states when to use delete versus patch/position or any exclusions. Usage is implied rather than guided.

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