Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Update Paragraph Style

update_paragraph_style

Apply heading styles, list formatting, and paragraph properties like alignment, spacing, and indentation to a selected range in Google Docs.

Instructions

Apply paragraph-level formatting, heading styles, and/or list formatting to a range in a Google Doc.

This tool can apply named heading styles (H1-H6) for semantic document structure, create bulleted or numbered lists with nested indentation, and customize paragraph properties like alignment, spacing, and indentation. All operations can be applied in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoOptional document tab ID to target
alignmentNoText alignment - 'START' (left), 'CENTER', 'END' (right), or 'JUSTIFIED'
directionNoParagraph direction - 'LEFT_TO_RIGHT' or 'RIGHT_TO_LEFT'
end_indexYesEnd position (exclusive) - should cover the entire paragraph
list_typeNoCreate a list from existing paragraphs ('UNORDERED' for bullets, 'ORDERED' for numbers, 'CHECKBOX' for checklists)
indent_endNoRight/end indent in points
segment_idNoOptional header/footer/footnote segment ID to target
border_dashNoBorder dash style ('SOLID', 'DOT', or 'DASH'; defaults to 'SOLID')
document_idYesDocument ID to modify
space_aboveNoSpace above paragraph in points (e.g., 12 for one line)
space_belowNoSpace below paragraph in points
start_indexYesStart position using Docs API indices from inspect_doc_structure. For the main body, 0 is also accepted as an alias for the first writable position.
border_colorNoBorder color (#RRGGBB; defaults to black)
border_edgesNoParagraph border edges to update ('top', 'bottom', 'left', 'right', or 'between'); omit to update all four outer edges
border_widthNoBorder width in points (defaults to 1)
indent_startNoLeft/start indent in points
line_spacingNoLine spacing multiplier (1.0 = single, 1.5 = 1.5x, 2.0 = double)
spacing_modeNo'NEVER_COLLAPSE' or 'COLLAPSE_LISTS'
bullet_presetNoOptional explicit Google Docs bullet preset
heading_levelNoHeading level 0-6 (0 = NORMAL_TEXT, 1 = H1, 2 = H2, etc.) Use for semantic document structure
shading_colorNoParagraph shading/background color (#RRGGBB)
border_paddingNoBorder padding in points (defaults to 4)
keep_with_nextNoKeep the paragraph with the next paragraph
named_style_typeNoDirect named style type - 'NORMAL_TEXT', 'TITLE', 'SUBTITLE', 'HEADING_1' through 'HEADING_6'. Mutually exclusive with heading_level.
indent_first_lineNoFirst line indent in points (e.g., 36 for 0.5 inch)
page_break_beforeNoStart the paragraph on a new page
user_google_emailYesUser's Google email address
list_nesting_levelNoNesting level for lists (0-8, where 0 is top level, default is 0) Use higher levels for nested/indented list items
keep_lines_togetherNoKeep all lines of the paragraph together
avoid_widow_and_orphanNoAvoid widows/orphans for the paragraph

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=false, so the agent knows this is a mutation. The description adds that multiple formatting operations can be combined in a single call, which is useful context. However, it does not disclose potential side effects, permissions, or behavior on invalid indices.

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?

Two sentences, front-loaded with purpose, no redundant text. Efficiently summarizes the tool's capability.

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

Completeness4/5

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

The tool has 30 parameters and an output schema, and the schema fully documents parameters. The description provides a clear high-level overview of the tool's purpose and combinations, though it could mention using indices from inspect_doc_structure but that's already in the parameter description.

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 coverage is 100%, with each parameter having a description. The tool description adds no parameter-specific semantics beyond what the schema already provides, so a baseline score 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 opens with a specific verb ('Apply') and names the resource ('paragraph-level formatting, heading styles, and/or list formatting to a range in a Google Doc'). It clearly differentiates from sibling tools that handle text insertion or document-wide updates.

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?

The description implies usage by stating what it can do and that all operations can be applied in a single call, but it does not explicitly name alternative tools or exclusion criteria. It provides clear context for when to choose this tool for paragraph styling.

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/taylorwilsdon/google_workspace_mcp'

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