Skip to main content
Glama
adexltd

MCP Google Suite

by adexltd

docs_create

Create a new Google Doc with a title and optional initial content through Google Workspace integration.

Instructions

Create a new Google Doc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the document
contentNoInitial content

Implementation Reference

  • The primary MCP tool handler for 'docs_create'. Extracts title and optional content from input arguments, validates title, logs the action, calls DocsService.create_document, and returns the result.
    async def _handle_docs_create(
        self, context: GoogleWorkspaceContext, arguments: dict
    ) -> Dict[str, Any]:
        """Handle docs create requests."""
        title = arguments.get("title")
        content = arguments.get("content")
    
        if not title:
            raise ValueError("Document title is required")
    
        logger.debug(f"Creating document - Title: {title}, Content length: {len(content or '')}")
        result = await context.docs.create_document(title=title, content=content)
        logger.debug(f"Document created - ID: {result.get('documentId')}")
        return result
  • Input schema definition for the 'docs_create' tool, specifying title as required string and content as optional string.
    types.Tool(
        name="docs_create",
        description="Create a new Google Doc",
        inputSchema={
            "type": "object",
            "properties": {
                "title": {"type": "string", "description": "Title of the document"},
                "content": {"type": "string", "description": "Initial content"},
            },
            "required": ["title"],
        },
    ),
  • Dynamic registration code that maps the 'docs_create' tool name to its handler '_handle_docs_create' in the tool registry.
    handler_name = f"_handle_{tool.name}"
    if hasattr(self, handler_name):
        handler = getattr(self, handler_name)
        self._tool_registry[tool.name] = handler
        logger.debug(f"Registered handler for {tool.name}")
  • Helper method in DocsService that performs the actual Google Docs API call to create a new document and optionally updates it with initial content.
    async def create_document(self, title: str, content: Optional[str] = None) -> Dict[str, Any]:
        """Create a new Google Doc with optional initial content."""
        try:
            service = await self.get_service()
            doc = await asyncio.to_thread(service.documents().create(body={"title": title}).execute)
    
            if content:
                await self.update_document_content(doc["documentId"], content)
    
            return {"success": True, "document": doc}
        except HttpError as error:
            return {"success": False, **self.handle_error(error)}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the creation action without details on permissions, rate limits, response format, or error handling. It doesn't contradict annotations, but fails to provide necessary context for a mutation tool.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, or return values, leaving significant gaps in understanding how to use this tool effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents both parameters. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage but not enhancing understanding.

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

Purpose4/5

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

The description clearly states the action ('Create') and resource ('a new Google Doc'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'sheets_create' or 'drive_create_folder' beyond specifying the Google Doc type, missing explicit sibling distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'sheets_create' or 'drive_create_folder'. The description lacks context about use cases, prerequisites, or exclusions, offering only a basic statement of function without operational guidance.

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/adexltd/mcp-google-suite'

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