Skip to main content
Glama
dipseth

google-workspace-unlimited

Forward Gmail Message

forward_gmail_message

Forward a Gmail message to specified recipients while preserving original HTML formatting. Optionally add your own text before the forwarded content.

Instructions

Forward a Gmail message to specified recipients with HTML formatting preservation and elicitation support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipients (optional)
toNoRecipient email address(es)myself
bccNoBCC recipients (optional)
bodyNoOptional additional message body to add before the forwarded content. Usage depends on content_type: 'plain' = plain text only, 'html' = HTML content, 'mixed' = plain text (HTML in html_body)
html_bodyNoHTML content when content_type='mixed'. This will be added before the forwarded HTML content. Ignored for 'plain' and 'html' types
message_idYesThe ID of the Gmail message to forward. This will include the original message content and headers
content_typeNoContent type: 'plain' (converts original HTML to text), 'html' (preserves HTML formatting), 'mixed' (both plain and HTML versions - recommended)mixed
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
errorNo
actionNo
draftIdNo
subjectNo
successYes
userEmailYes
content_typeYes
forwarded_toNo
cc_recipientsNo
to_recipientsNo
bcc_recipientsNo
html_preservedNo
forward_message_idNo
elicitationRequiredNo
original_message_idYes
recipientsNotAllowedNo
elicitationNotSupportedNo
Behavior3/5

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

The description discloses one key behavior: HTML formatting preservation. However, the term 'elicitation support' is undefined, and no information about permissions, side effects, or limitations is given. Annotations are minimal, so the description carries moderate burden.

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?

Single sentence with verb-initial structure. Every word contributes meaning. No wasted tokens.

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?

Given the tool's complexity (8 parameters, output schema exists), the description is adequate but lacks detail on return values, error conditions, or the meaning of 'elicitation support'. The user must rely heavily on the schema and parameter descriptions.

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%, so the description adds limited value beyond the schema. The only added hint is 'elicitation support', which is not reflected in the schema parameters. Baseline of 3 is appropriate.

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 primary action (forward Gmail message) and mentions HTML formatting preservation. The term 'elicitation support' is ambiguous but does not obscure the main purpose. The tool is distinct from siblings like draft_gmail_forward (which only drafts) and reply_to_gmail_message.

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 is provided on when to use this tool vs. alternatives like draft_gmail_forward, reply_to_gmail_message, or send_gmail_message. No conditions, prerequisites, or exclusions are mentioned.

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