Skip to main content
Glama

format_all_slides_text

Apply character formatting (bold, italic, font, size, color) to every text element in a Google Slides deck or a single slide via one batch update.

Instructions

Bulk-apply character formatting to every text element on a slide or deck.

Walks the presentation, collects every page element containing text, and issues one updateTextStyle per element in a single batchUpdate. For a specific element use format_slides_text. For paragraph-level rules (alignment, spacing) use format_slides_paragraph. Requires the presentations OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
presentation_idYesTarget presentation ID.
page_object_idNoSlide objectId to scope the restyle to that one slide. Omit to restyle every slide in the deck.
boldNoTrue to bold, False to unbold, None to leave unchanged.
italicNoSame semantics as bold.
underlineNoSame semantics as bold.
strikethroughNoSame semantics as bold.
font_familyNoFont family name, e.g. "Arial".
font_sizeNoFont size in points.
text_colorNoHex color like "#333333".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes internal behavior: walks presentation, collects text elements, issues one updateTextStyle per element in a single batchUpdate. No annotations exist, so description fully carries the burden.

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 sentences, each valuable: purpose, internal mechanics, sibling differentiation, auth requirement. No unnecessary words.

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?

Covers batch behavior, sibling alternatives, OAuth scope. Output schema exists, so return values are documented. Complete for the tool's complexity.

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?

Input schema has 100% description coverage, so baseline 3. Description does not add additional parameter meaning, but not required.

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 the tool bulk-applies character formatting to every text element on a slide or deck, distinguishing it from siblings format_slides_text and format_slides_paragraph.

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?

Explicitly instructs when to use this tool vs alternatives: for a specific element use format_slides_text, for paragraph-level rules use format_slides_paragraph. Also mentions required OAuth scope.

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