Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

docs_create

Create a new Google Doc in a specified Gmail account by providing the account ID and document title.

Instructions

Create a new Google Doc.

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": {
      "account": "<account>",
      "title": "<title>"
    },
    "name": "docs_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesDocument title.
accountYesAccount id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry transparency. It only states the core action and omits side effects (e.g., where the doc is saved, whether it returns an identifier, or what happens if a title is duplicated). This is a mutation with no behavioral disclosure beyond the act itself.

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, front-loaded sentence with no wasted words. It directly communicates the core action.

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?

Despite being a simple create tool, the description lacks essential contextual details: there is no output schema explaining return values, no annotation about safety or side effects, and no note about the destination or requirements. This leaves gaps for the agent in understanding the full impact of the tool.

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?

The input schema has 100% description coverage for both parameters ('title' and 'account') with clear definitions. The tool description adds no additional parameter semantics, but the schema already suffices, so a baseline of 3 is appropriate.

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 'Create a new Google Doc.' uses a specific verb ('Create') and resource ('Google Doc'), clearly distinguishing from sibling tools like docs_get (reading) and docs_append (modifying). It unambiguously identifies the tool's primary function.

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?

The description provides no guidance on when to use this tool or how it differs from related creation tools like sheets_create or upload_drive_file. It doesn't mention prerequisites such as account authentication or typical use cases.

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