Skip to main content
Glama
Sign In
fastmcp-gsuite

fastmcp-gsuite

by tumf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mark_gmail_message_read

Mark a specific Gmail message as read by providing the user's email and message ID. Update message status to keep your inbox organized.

Instructions

Mark a Gmail message as read.

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": {
      "user_id": "<user_id>",
      "message_id": "<message_id>"
    },
    "name": "mark_gmail_message_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe EMAIL of the Google account. Choose from:
message_idYesThe ID of the Gmail message to mark as read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action without mentioning side effects, error conditions, permissions, or idempotency, offering minimal transparency beyond the basic operation.

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 sentence with no wasted words, efficiently conveying the core purpose.

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

Completeness3/5

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

For a simple mutation tool with no output schema and high schema coverage, the description is adequate but missing behavioral context like error scenarios or return values. Given no annotations, it could provide more completeness.

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 coverage is 100% with both parameters described. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the parameters adequately.

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 'Mark a Gmail message as read' uses a specific verb ('mark') and resource ('Gmail message as read'), clearly distinguishing it from sibling tools like archive_gmail_message which moves messages out of the inbox.

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 modifying labels or archiving. The description does not specify prerequisites or context, leaving the agent without explicit usage direction.

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