Skip to main content
Glama
Sign In
aaronsb

Google Workspace MCP Server

by aaronsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

manage_scratchpad

Compose and edit multi-line text buffers with line or JSON edits, attach files, then send to Gmail, Docs, Sheets, Calendar, or Tasks.

Instructions

Compose, edit, and deliver text content. Use for any multi-line content: emails, documents, descriptions. Compose in the scratchpad, edit by line or JSON path, attach files, then send to any target. For short one-liners, use the service tool directly instead.

Input Schema

NameRequiredDescriptionDefault
keepNoFor send: keep scratchpad after successful send (default: true)
pathNoFor json_* ops: JSON path (e.g., $.config.name, $.items[0].value)
emailNoFor attach (drive source): account that can read the Drive file
labelNoFor create: optional human-readable label
refIdNoFor detach: attachment reference ID (att-1, att-2, etc.)
valueNoFor json_set, json_insert: value to set or insert (any JSON type)
fileIdNoFor attach (drive source): Drive file ID. The file is downloaded into the workspace at attach time.
formatNoFor create: content format (default: text). Controls validation and addressing mode.
sourceNoFor attach: file source (workspace or drive). For import: resource type (doc, email, sheet, drive_file).
targetNoFor send: delivery target
contentNoText content. For create (pre-fill), insert_lines, append_lines, replace_lines.
endLineNoEnd of line range (inclusive). For replace_lines, remove_lines, copy_lines, view.
filenameNoFor attach (workspace source): filename in workspace
afterLineNoInsert after this line number (0 = prepend). For insert_lines, copy_lines, attach.
operationYescreate: new buffer | view: show content | discard: free buffer | list: show all | insert_lines/append_lines/replace_lines/remove_lines: line editing | copy_lines: copy from another scratchpad | json_get/json_set/json_delete/json_insert: path-addressed JSON editing | attach/detach: file references | import: load from Google Workspace resource | send: deliver to target
startLineNoStart of line range (1-based). For replace_lines, remove_lines, copy_lines, view.
scratchpadIdNoScratchpad ID (sp-XXXX). Required for all operations except create and list.
sourceParamsNoFor import: source-specific parameters (e.g., { documentId, mode } for doc, { messageId } for email)
targetParamsNoFor send: target-specific parameters (e.g., { email, to, subject } for email, { filename } for workspace)
fromScratchpadIdNoFor copy_lines: source scratchpad ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.8.0
    • addedInput schema / properties / email
      Added value: +{
+  "description": "For attach (drive source): account that can read the Drive file",
+  "type": "string"
+}
    • changedInput schema / properties / fileId / description
      Previous value: -"For attach (drive source): Drive file ID"New value: +"For attach (drive source): Drive file ID. The file is downloaded into the workspace at attach time."
  2. First observedv4.5.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add lifecycle context the schema does not: a multi-step compose-edit-attach-send pipeline and delivery "to any target." However, it says nothing about buffer persistence across calls, whether send consumes the scratchpad, or auth/permission requirements for the delivery targets.

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

Conciseness4/5

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

Four short sentences, front-loaded with purpose then workflow then the exclusion rule. No filler, and the routing caveat is placed last where it belongs. Slightly dense for the number of concepts it compresses.

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

Completeness3/5

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

For a 17-operation tool with no annotations and no output schema, the description covers the workflow shape but omits return behavior, error cases, and state semantics (buffer lifetime, effect of send on the buffer). It is adequate orientation but not complete enough to call this tool confidently across all operations.

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 already documents all 20 parameters and the operation enum. The description adds only a high-level framing (line editing vs JSON-path editing vs attach), which is useful orientation but not meaning beyond what the schema provides.

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 states specific verbs and resources: compose/edit/deliver text content in a scratchpad buffer, with the concrete examples (emails, documents, descriptions) clarifying scope. It distinguishes itself from the sibling service tools by routing short one-liners elsewhere, though it never explains how it relates to the similarly-scoped manage_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?

It gives an explicit when-to-use rule ("any multi-line content") and a when-not rule ("For short one-liners, use the service tool directly instead"). The alternative is referred to only as "the service tool" rather than naming manage_email/manage_docs, which leaves the agent to infer which sibling applies.

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