Skip to main content
Glama
penysho

Google Docs MCP Server

by penysho

create_google_document

Generate and store new Google Docs by providing a title and optional initial content. Integrates with the Google Docs MCP Server for streamlined document creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoドキュメントの初期内容(オプション)
titleYes新しいドキュメントのタイトル

Implementation Reference

  • The executeInternal method implements the core logic of the 'create_google_document' tool: validates args, uses GoogleDocsService to create a new document with title and optional content, logs progress, and returns success response with document ID.
    protected async executeInternal(args: {
    	title: string;
    	content?: string;
    }): Promise<McpToolResponse> {
    	// 引数検証
    	this.validateArgs(args, ["title"]);
    
    	const { title, content = "" } = args;
    	this.logger.info(`ドキュメント作成開始: タイトル="${title}"`);
    
    	try {
    		// Google Docsサービスを取得
    		const docsService = await this.serviceContainer.getGoogleDocsService();
    
    		// ドキュメントを作成
    		const documentId = await docsService.createNewDocument(title, content);
    
    		this.logger.info(
    			`ドキュメント作成完了: ${documentId}, タイトル="${title}"`,
    		);
    
    		return this.createSuccessResponse(
    			`ドキュメントが作成されました。ID: ${documentId}`,
    		);
    	} catch (error) {
    		this.logger.error(`ドキュメント作成エラー: タイトル="${title}"`, error);
    		throw error; // BaseMcpToolでエラーハンドリング
    	}
    }
  • The schema getter defines the input schema for the tool using Zod: required 'title' string and optional 'content' string.
    get schema() {
    	return {
    		title: z.string().describe("新しいドキュメントのタイトル"),
    		content: z
    			.string()
    			.optional()
    			.describe("ドキュメントの初期内容(オプション)"),
    	};
    }
  • Instantiation and registration of the CreateDocumentTool (named 'create_google_document') in the ToolRegistry's registerDefaultTools method.
    this.registerTool(new CreateDocumentTool(this.serviceContainer));
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/penysho/docs-mcp'

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