Skip to main content
Glama

format_slides_paragraph

Apply paragraph alignment, line spacing, spacing above/below, and bullet lists to text in a Google Slide shape, text box, or table cell.

Instructions

Apply paragraph-level formatting (alignment, spacing, bullets) to text inside a shape, text box, or table cell on a Google Slide.

Use this for paragraph concerns — alignment, line spacing, space above/below, bullet lists. For character-level styling (bold, font size, color), use format_slides_text instead. For styling the shape itself (fill, outline, shadow), use style_slides_shape.

Requires OAuth scope: https://www.googleapis.com/auth/presentations (write). Idempotent: re-running with the same values is safe. No rate limits beyond Google Slides API defaults (~300 req/min per user).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
page_element_idYesObject ID of the target shape/text box/table cell. Get it from `get_presentation` or `get_page`. Must be a text-bearing element; passing an image element will return a no-op error.
alignmentNoParagraph horizontal alignment. One of `START` (left), `CENTER`, `END` (right), `JUSTIFIED`. Omit to leave unchanged.
line_spacingNoLine spacing as percentage — `100.0` = single-spaced, `115.0` = 1.15x (Google Docs default), `150.0` = 1.5x, `200.0` = double. Omit to leave unchanged.
space_aboveNoPoints of space above each paragraph (e.g., `12` for ~12pt gap). Omit to leave unchanged.
space_belowNoPoints of space below each paragraph. Omit to leave unchanged.
bullet_presetNoBullet list preset name from the Google Slides API, e.g., `BULLET_DISC_CIRCLE_SQUARE`, `BULLET_DIAMONDX_ARROW3D_SQUARE`, `NUMBERED_DIGIT_ALPHA_ROMAN`, `NUMBERED_UPPERALPHA_ALPHA_ROMAN`. Pass `NONE` (uppercase) to REMOVE existing bullets. Omit to leave bullet state unchanged.
start_indexNoOptional 0-based character offset within the element's text where formatting starts. When both start/end are omitted, formatting applies to ALL paragraphs in the element.
end_indexNoOptional 0-based character offset (exclusive) where formatting ends. Must be greater than start_index if both provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Given no annotations, description fully carries burden: discloses OAuth write scope, idempotent behavior, safe re-execution, rate limit context, and a specific error case (image element returns no-op). No contradictions.

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?

Three-sentence structure: purpose, guidelines, behavioral notes. No fluff, front-loaded with key info. Every sentence adds distinct value.

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?

With output schema present, return values not needed. Description covers how to obtain page_element_id, scope requirements, error behavior, and parameter application scope (all paragraphs vs. range). Complete for a 10-param formatting tool.

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

Parameters4/5

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

Schema coverage is high (90%), but the description adds value by summarizing parameter groups (alignment, spacing, bullets) and clarifying 'Omit to leave unchanged' for each. Bullet preset examples add meaning beyond enum-less schema.

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?

Clearly states verb+resource: 'Apply paragraph-level formatting (alignment, spacing, bullets) to text inside a shape, text box, or table cell on a Google Slide.' Explicitly distinguishes from siblings format_slides_text and style_slides_shape.

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

Usage Guidelines5/5

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

Provides explicit when-to-use (paragraph concerns) and when-not-to (character-level, shape styling) with specific alternative tool names. Also mentions idempotence and rate limits for safe usage.

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/HuntsDesk/ve-gws'

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