Skip to main content
Glama
dipseth

google-workspace-unlimited

Manage Chat Space

manage_space

Manage Google Chat spaces: add/remove members, create/update spaces, and handle messages and reactions.

Instructions

Unified tool for Google Chat space administration: manage members, create/update/delete spaces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiNoUnicode emoji for add_reaction (e.g., '🚀', '👍').
actionYesAction to perform. Space/member actions: 'list_members', 'add_member', 'remove_member', 'create_space', 'update_space', 'delete_space'. Message actions: 'get_message', 'update_message', 'delete_message'. Reaction actions (require delegated user auth): 'add_reaction', 'list_reactions', 'delete_reaction'.
space_idNoSpace resource name (e.g., 'spaces/AAQAKl_yP9Y'). Required for list_members, add_member, update_space, delete_space.
space_typeNoType of space to create. Default: SPACE.
descriptionNoDescription for create_space or update_space.
member_nameNoFull member resource name (e.g., 'spaces/xxx/members/yyy'). Required for remove_member.
member_roleNoRole for the member. Default: ROLE_MEMBER.
display_nameNoDisplay name for create_space or update_space.
member_emailNoEmail address of the member to add. Required for add_member.
message_nameNoFull message resource name (e.g., 'spaces/xxx/messages/yyy'). Required for get/update/delete_message and reaction actions.
message_textNoNew message text for update_message. Supports @mentions via <users/email> format.
reaction_nameNoFull reaction resource name (e.g., 'spaces/xxx/messages/yyy/reactions/zzz'). Required for delete_reaction.
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
errorNo
actionYes
messageYes
spaceIdYes
successYes
Behavior3/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description does not add behavioral context beyond 'administration', relying on schema details for actions like delegation (reactions). No contradictions, but minimal additional transparency.

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 description is a single sentence, concise but incomplete. It omits key actions (message and reactions), reducing accuracy. Front-loads the purpose but lacks structured detail.

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

Completeness2/5

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

The description does not cover the full scope of actions available (missing message and reaction actions). Given 13 parameters and existing output schema, the description should provide a more complete overview. It is insufficient for an agent to understand the tool's full capabilities.

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 has 13 parameters with 100% description coverage. The description does not elaborate on parameter meanings, as the schema already provides details. Baseline score of 3 is appropriate for full schema coverage.

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 description clearly states it is a unified tool for Google Chat space administration, covering member management and space CRUD. However, it omits message and reaction actions that are present in the action enum, making it slightly incomplete. It distinguishes from sibling tools like 'send_message' by focusing on administration rather than messaging.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'list_spaces' or 'send_message'. The description labels it as 'unified' but does not explain its specific use cases or exclusions. The action enum provides implicit context, but no explicit usage recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipseth/google_workspace_fastmcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server