Skip to main content
Glama

read_document

Read-only

Read a Google Doc by URL or ID, retrieving content as markdown or plain text in bounded chunks. Supports multi-tab documents, outlines, and optional colored text spans.

Instructions

Read a Google Doc (item = URL or ID) as 'markdown' (default) or 'text', one bounded chunk at a time.

Multi-tab docs: by default every tab is read (each prefixed with its title as a heading);
pass a `tab` id, or an `item` URL containing `tab=t.xxxx`, to read only that tab. Returns the
requested chunk (0-based) plus title, the doc's `tabs`, the outline, and paging metadata
(total_chunks, total_chars, has_more). Set max_chars<=0 to get the whole document. Set
include_colors=true to also return `colored_runs` (text spans with an explicit foreground color).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabNo
itemYes
chunkNo
max_charsNo
output_formatNomarkdown
include_colorsNo
Behavior5/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, and the description adds behavioral details beyond these: chunked reading, paging metadata, return fields (title, tabs, outline), and special behaviors like reading all tabs by default. No contradictions.

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, well-organized paragraph that front-loads the core action and parameter types. Every sentence adds value, with no fluff or repetition.

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?

Despite having no output schema, the description details return values (title, tabs, outline, paging metadata). Parameters are all explained, and the tool's behavior (chunked, bounded) is fully described. Annotations cover safety and openness, making this complete for the complexity level.

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?

Input schema has 0% description coverage (no descriptions for properties), but the tool description provides clear semantics for all parameters: tab usage, chunk as 0-based, max_chars<=0 for whole doc, include_colors for colored_runs, output_format default. This significantly compensates for the bare 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 specifies the verb 'Read', the resource 'Google Doc', and critical details like input format (URL or ID) and output formats (markdown or text). It is unique among siblings: other tools read comments or files, not docs.

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

Usage Guidelines4/5

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

The description explains when to use the tab parameter, how multi-tab works, and options like max_chars or include_colors. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., read_comments for reading comments only).

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/shivankj11/gdrive-mcp'

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