grr

Overview Schema Source Related Servers Discussions Admin

chat.users.availability.markAsActive

Marks the authenticated user as ACTIVE in Google Chat until a set expiration, then reverts to AWAY.

Instructions

Marks user as ACTIVE in Google Chat. Sets the user's availability state to ACTIVE. The ACTIVE state lasts until the specified expiration, at which point the user's state becomes AWAY. Note that if the user is actively using Chat, the ACTIVE state duration may extend beyond the provided expiration. This method only updates the authenticated user's availability. Requires user authentication with authorization scope: - h [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 MarkAsActiveRequest object accepting expireTime, ttl; pass it via paramsor whole viabody_file` Siblings over the same resource: get, markAsAway, markAsDoNotDisturb, patch.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. The resource name of the availability to mark as active. Format: users/{user}/availability `{user}` is the id for the Person in the People API or Admi
`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 MarkAsActiveRequest object.
`request_body`	No	Request body of type MarkAsActiveRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`name`	No
`state`	No
`customStatus`	No
`doNotDisturbMetadata`	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 MarkAsActiveRequest object."

addedInput schema / properties / request_body

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

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Required. The resource name of the availability to mark as active. Format: users/{user}/availability `{user}` is the id for the Person in the People API or Admi"New value: +"[URL path segment] Required. The resource name of the availability to mark as active. Format: users/{user}/availability `{user}` is the id for the Person in the People API or Admi"

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "customStatus": {
+      "properties": {
+        "emoji": {
+          "properties": {
+            "customEmoji": {
+              "properties": {
+                "emojiName": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "payload": {
+                  "type": "object"
+                },
+                "temporaryImageUri": {
+                  "type": "string"
+                },
+                "uid": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "unicode": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "expireTime": {
+          "type": "string"
+        },
+        "text": {
+          "type": "string"
+        },
+        "ttl": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "doNotDisturbMetadata": {
+      "properties": {
+        "expirationTime": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "state": {
+      "enum": [
+        "STATE_UNSPECIFIED",
+        "ACTIVE",
+        "IDLE",
+        "AWAY",
+        "DO_NOT_DISTURB"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the behavioral burden well: it explains the ACTIVE state expiration, the fallback to AWAY, the possibility of extension when the user is actively using Chat, authentication requirements, and that the operation is an HTTP POST refused under --readonly safety profiles.

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 front-loaded with the core action and state behavior, and most sentences add relevant context. However, it contains some redundancy and a malformed fragment around the HTTP POST/readonly note, which slightly reduces clarity.

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 mutation tool with no annotations and an existing output schema, the description is complete enough: it covers state semantics, authentication, request-body handling, readonly refusal, and sibling alternatives. Return-value details can be safely omitted because an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already provides parameter documentation. The description adds useful invocation context by identifying the request body as MarkAsActiveRequest with expireTime and ttl fields and explaining that it can be passed via params or body_file, though it does not clarify the distinction between expireTime and ttl.

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 states a specific verb and resource: marks the authenticated user as ACTIVE in Google Chat and sets their availability state. It also names the sibling methods over the same resource (get, markAsAway, markAsDoNotDisturb, patch), so an agent can distinguish this operation from related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clarifies that this method only updates the authenticated user's availability and requires user authentication with a specific authorization scope. It also lists sibling methods, which gives clear alternatives, though it stops short of explicitly saying when to choose markAsActive versus markAsAway or markAsDoNotDisturb.

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

Deploy Server