Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

insert_markdown

Convert Markdown text into native Google Docs formatting and insert it into a document at a specified position, supporting headings, lists, bold, italic, links, code blocks, blockquotes, checklists, and mentions.

Instructions

Insert Markdown-formatted content into a Google Doc.

Converts Markdown syntax (headings, bold, italic, lists, links, code blocks,
blockquotes) into native Google Docs formatting via batchUpdate requests.

Args:
    user_google_email: User's Google email address.
    document_id: ID of the document to update (supports A-Z aliases from search).
    markdown_text: Markdown string to convert and insert.
    index: Document index to start insertion at (1-based, default: 1).
           Index 1 is the start of the document body.
    checklist_mode: Checklist rendering mode for markdown task lists:
                    `unicode` (default) or `native`.
    mention_mode: Mention rendering mode for markdown mentions:
                  `text` (default) or `person_chip`.
    dry_run: When True (default), return planned mutation without executing it

Returns:
    str: Confirmation message with document link and request count.

Example:
    insert_markdown(
        document_id="abc123",
        markdown_text="# Welcome

This is bold and italic text.

  • Item 1

  • Item 2" )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
document_idYes
markdown_textYes
indexNo
checklist_modeNounicode
mention_modeNotext
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so the description fully covers behavioral traits. It explains the conversion process via batchUpdate requests, defaults for index, checklist_mode, mention_mode, and the dry_run parameter's effect. It discloses return type as a confirmation string with link and request count. Could mention write access requirements or error handling, but overall sufficient.

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?

The description is well-structured with a front-loaded purpose sentence, followed by an Args/Returns/Example format. It is somewhat lengthy but each sentence adds value. Minor redundancy (e.g., repeated 'Insert Markdown-formatted content') could be trimmed, but overall effective.

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

Completeness5/5

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

Given 7 parameters, no annotations, and an existing output schema, the description provides a complete guide. It covers all parameters, their defaults, the dry_run mode, return value, and an example. Lacks only prerequisites like authentication, but that is implied by the user_google_email parameter. Highly complete for agent 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?

Input schema has 0% description coverage, but the description adds detailed semantics for all 7 parameters. It explains index as 1-based with default 1, checklist and mention modes with options, and dry_run's default and purpose. This fully compensates for the schema lack, making each parameter's role clear.

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 clearly states it inserts Markdown-formatted content into a Google Doc, listing specific Markdown elements converted. It distinguishes from siblings like batch_update_doc and insert_doc_elements by specifying Markdown conversion, making the tool's unique purpose clear.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It only states the action without comparing to other document update tools in the sibling list, leaving the agent to infer usage context.

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/Skeptomenos/google-workspace-mcp-advanced'

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