Skip to main content
Glama
Sign In
Google MCP

Google MCP

by vakharwalad23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

google_gmail_modify_labels

Manage Gmail labels by adding or removing them from specific emails using the message ID. Integrates with AI clients for efficient email organization.

Instructions

Add or remove labels from an email

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "messageId": "<messageId>"
    },
    "name": "google_gmail_modify_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
addLabelIdsNoLabels to add to the message
messageIdYesID of the email to modify
removeLabelIdsNoLabels to remove from the message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool modifies labels (implying mutation) but doesn't disclose behavioral traits like whether it requires specific permissions, if changes are reversible, rate limits, or what happens if label IDs don't exist. For a mutation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a tool with clear parameters and no complex behavior to explain.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, updated email object), error conditions, or important behavioral context needed for safe use.

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 the schema already documents all three parameters (messageId, addLabelIds, removeLabelIds) with clear descriptions. The description adds no additional meaning beyond what the schema provides, which meets the baseline of 3 when schema coverage is high.

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 the action ('Add or remove') and resource ('labels from an email'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools in the Gmail domain (like google_gmail_list_labels or google_gmail_get_email), which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an existing email ID), when not to use it, or how it relates to other Gmail tools (e.g., use google_gmail_list_labels first to get label IDs).

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

Related Tools