Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

manage_gmail_label

Create, update, or delete Gmail labels for a specified user to organize email messages.

Instructions

Manages Gmail labels: create, update, or delete labels.

Args: user_google_email (str): The user's Google email address. Required. action (Literal["create", "update", "delete"]): Action to perform on the label. name (Optional[str]): Label name. Required for create, optional for update. label_id (Optional[str]): Label ID. Required for update and delete operations. label_list_visibility (Literal["labelShow", "labelHide"]): Whether the label is shown in the label list. message_list_visibility (Literal["show", "hide"]): Whether the label is shown in the message list. dry_run (bool): If True, preview label changes without applying mutations.

Returns: str: Confirmation message of the label operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
actionYes
nameNo
label_idNo
label_list_visibilityNolabelShow
message_list_visibilityNoshow
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description must cover safety. It discloses actions and the dry_run parameter for previewing changes without applying mutations. Does not mention authentication requirements or error handling, but covers core behavior well.

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?

Well-structured with a clear purpose statement followed by parameter descriptions. Efficient but slightly lengthy; no wasted lines.

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 tool complexity (3 actions, 7 params) and presence of output schema, the description provides sufficient context for correct invocation. Covers all action-specific constraints.

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?

Despite schema coverage at 0%, the description explains each parameter's role, including conditional requirements (e.g., label_id required for update/delete). Adds significant meaning beyond the raw schema.

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?

Clearly states the tool manages Gmail labels with create, update, or delete actions. Distinguishes from sibling tools like list_gmail_labels which is read-only.

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?

Implies usage for label CRUD operations but lacks explicit guidance on when to use alternatives or when not to use this tool. No mention of prerequisites or 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/Skeptomenos/google-workspace-mcp-advanced'

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