Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by risvan1605
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

read_google_doc

Extract full text content from any Google Document by providing its ID. Returns document title, text, and URL.

Instructions

Read the full content of a Google Document.

Extracts all text content from the document, preserving paragraph structure.

Args: document_id: The ID of the Google Document to read (found in the document URL).

Returns: Document ID, title, full text content, and URL.

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": {
      "document_id": "<document_id>"
    },
    "name": "read_google_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Discloses that it extracts text preserving paragraph structure, and returns doc ID, title, content, and URL. However, with no annotations, it does not cover auth requirements, rate limits, or read-only nature beyond the verb 'Read'.

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?

Straightforward three sentences: purpose, extraction detail, and Args/Returns section. Front-loaded with clear verb and resource. No redundancy.

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?

For a simple read tool with one parameter and no annotations or output schema, description adequately covers usage and return values. Could mention error handling or permissions, but overall complete enough for typical use.

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?

Single parameter 'document_id' is described with a helpfultip on where to find it ('found in the document URL'), adding meaning beyond the schema which only has a title. Schema coverage is 0%, but description compensates fully.

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?

Description clearly states 'Read the full content of a Google Document,' using a specific verb and resource. It distinguishes from sibling tools like append_to_google_doc and get_google_doc_metadata by explicitly focusing on reading full content.

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

Usage Guidelines3/5

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

Implied usage (use to read document content) but no explicit guidance on when to use vs alternatives like get_google_doc_metadata. Does not mention exclusions or prerequisites.

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