Skip to main content
Glama

create_collaborative_inbox_group

Creates a new Google Group configured as a Collaborative Inbox, enabling shared email management. Sets up posting permissions and adds initial members.

Instructions

    Creates a new Google Group configured as a Collaborative Inbox.
    
    Args:
        group_email: The email address for the new group.
        group_name: The display name for the new group.
        initial_member_emails: List of email addresses to add as members.
        who_can_post: Posting permission setting. Defaults to "ALL_MEMBERS_CAN_POST".
        confirmed: Must be True to execute. If False, returns a preview.
        
    GAM pattern:
        1. gam create group <group_email> name <group_name>
        2. gam update group <group_email> setting isArchived false whoCanPostMessage <who_can_post> enableCollaborativeInbox true
        3. for each member: gam update group <group_email> add member <member_email>
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedNo
group_nameYes
group_emailYes
who_can_postNoALL_MEMBERS_CAN_POST
initial_member_emailsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Description discloses the preview behavior when confirmed=False, but does not mention authorization requirements, error states (e.g., if group exists), or any rate limits. With no annotations, the burden is higher, and missing details reduce transparency.

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?

Description is concise, with a clear header, parameter list, and GAM pattern. Could be slightly more structured (e.g., bullet points), but it is front-loaded and each sentence adds value.

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?

Given five parameters (three required), no enums, and an output schema, the description covers all parameter semantics, execution behavior (preview vs execute), and the underlying GAM pattern. It is complete for the tool's complexity.

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

Parameters5/5

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

All five parameters are described with purpose and defaults (who_can_post) or special behavior (confirmed). Schema coverage is 0%, so description fully compensates, adding meaning beyond raw parameter names.

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?

Description clearly states it creates a Google Group configured as a Collaborative Inbox, with specific verb and resource. It distinguishes from sibling tools (e.g., audit tools, run_gam_command) by focusing on this specific creation task.

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?

Description explains the 'confirmed' parameter for execution vs preview, and lists GAM steps, but does not explicitly state when to use this tool over alternatives like run_gam_command or validate_gam_command. Context is clear but lacks exclusions.

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/ktibbs9417/gamcp'

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