Skip to main content
Glama

get_doc_content

Extract body text from Google Docs or Drive-stored .docx files, with support for nested tab content.

Instructions

Retrieve Doc body text (native Google Docs or Drive-stored .docx).

For native Google Docs uses the Docs API and walks tabs (including nested child tabs). For non-native Drive files (.docx, etc.) falls back to the Drive download + text extraction path. For markdown output use get_doc_as_markdown; for structural inspection (style, headings, objects) use inspect_doc_structure. Requires both drive.readonly and docs.readonly OAuth scopes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
document_idYesDoc ID or a full URL like docs.google.com/document/d/<id>/edit (either is accepted).
suggestions_view_modeNoHow tracked-changes are rendered: "DEFAULT_FOR_CURRENT_ACCESS" (default), "SUGGESTIONS_INLINE" (show suggestions inline), "PREVIEW_SUGGESTIONS_ACCEPTED" (render as if accepted), or "PREVIEW_WITHOUT_SUGGESTIONS" (render as if rejected).DEFAULT_FOR_CURRENT_ACCESS

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes internal behavior: uses Docs API for native docs and walks tabs; falls back to Drive download for .docx. Required scopes are listed. No annotations provided, so description carries full burden and does so well.

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?

Three concise sentences, front-loaded with purpose, then behavior and alternatives, then scopes. No unnecessary words.

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

Completeness4/5

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

Covers purpose, behavior, alternatives, and scopes adequately for a content retrieval tool. With output schema present, no need to describe return values. Minor omission: no mention of error handling for missing documents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions; description adds value by noting that document_id accepts full URLs, going beyond 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?

The description clearly states the tool retrieves Doc body text for both native Google Docs and .docx files, and distinguishes from siblings like get_doc_as_markdown and inspect_doc_structure.

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 provides alternatives: 'For markdown output use get_doc_as_markdown; for structural inspection use inspect_doc_structure.' Also mentions required OAuth scopes, guiding appropriate use.

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/HuntsDesk/ve-gws'

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