Google Workspace MCP Server

Overview Schema Source Related Servers Discussions Admin

get_doc_as_markdown

Convert a Google Doc to Markdown, preserving headings, bold, italics, links, lists, and tables, with comment threads and anchor text for full context.

Instructions

Reads a Google Doc and returns it as clean Markdown with optional comment context.

Unlike get_doc_content which returns plain text, this tool preserves document formatting as Markdown: headings, bold/italic/strikethrough, links, code spans, ordered/unordered lists with nesting, and tables.

When comments are included (the default), each comment's anchor text — the specific text the comment was attached to — is preserved, giving full context for the discussion.

Args: user_google_email: User's Google email address document_id: ID of the Google Doc (or full URL) include_comments: Whether to include comments (default: True) comment_mode: How to display comments: - "inline": Footnote-style references placed at the anchor text location (default) - "appendix": All comments grouped at the bottom with blockquoted anchor text - "none": No comments included include_resolved: Whether to include resolved comments (default: False)

Returns: str: The document content as Markdown, optionally with comments

Input Schema

TableJSON Schema

Name	Required	Default
`document_id`	Yes
`comment_mode`	No	inline
`include_comments`	No
`include_resolved`	No
`user_google_email`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.14.3Sep 6, 2026

TDQS

A5/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses defaults for include_comments and include_resolved, explains comment_mode values, describes how anchor text is preserved, and signals a read operation by using 'Reads'. This goes well beyond the bare schema.

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 core purpose and sibling differentiation are front-loaded in the first sentences. The Args and Returns sections are structured and skimmable, and no sentence is wasted.

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?

For a read-only conversion tool with 5 parameters, the description covers purpose, all parameters, defaults, comment behavior, and return type. It is complete enough for an agent to invoke correctly without needing extra context.

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?

The input schema has no parameter descriptions (0% coverage), so the Args block is essential. It documents all five parameters, explains the meaning of comment_mode values, and clarifies that document_id can be a full URL, adding value beyond the schema's type-only fields.

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?

States a specific verb ('Reads'), resource ('Google Doc'), and output format ('Markdown'), and explicitly contrasts with sibling get_doc_content so an agent can distinguish it. The mention of headings, lists, and tables makes the output concrete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly identifies the alternative (get_doc_content) and the differentiator: this tool preserves formatting as Markdown while get_doc_content returns plain text. It also states default comment behavior, helping an agent decide when to rely on defaults.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server