Skip to main content
Glama
HuntsDesk

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

create_slides_text_box

Add a text box to a slide with specified text, position, size, and font styling using EMU units.

Instructions

Add a text box to a slide with initial content and position.

Use this for text content; use create_slides_shape for geometric shapes (rectangles, callouts, arrows). To edit text inside an existing element use batch_update_presentation with insertText / deleteText. All positions are in EMU (English Metric Units): 914400 EMU = 1 inch, 12700 EMU = 1 point. 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_idYesSlide objectId where the box is placed (from get_presentation.slides[].objectId).
textYesInitial text content for the box.
leftNoX offset from slide's left edge in EMU. Default 914400 (1 in).
topNoY offset from top in EMU. Default 914400 (1 in).
widthNoBox width in EMU. Default 3000000 (≈3.28 in).
heightNoBox height in EMU. Default 1000000 (≈1.09 in).
font_sizeNoFont size in points for the initial text.
boldNoTrue to bold the initial text.
italicNoTrue to italicize the initial text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv1.0.0
    • addedInput schema / properties / bold / description
      Added value: +"True to bold the initial text."
    • addedInput schema / properties / font_size / description
      Added value: +"Font size in points for the initial text."
    • addedInput schema / properties / height / description
      Added value: +"Box height in EMU. Default 1000000 (≈1.09 in)."
    • addedInput schema / properties / italic / description
      Added value: +"True to italicize the initial text."
    • addedInput schema / properties / left / description
      Added value: +"X offset from slide's left edge in EMU. Default 914400\n(1 in)."
    • changedInput schema / properties / page_object_id / description
      Previous value: -"Object ID of the slide to add the text box to."New value: +"Slide objectId where the box is placed (from\nget_presentation.slides[].objectId)."
    • addedInput schema / properties / presentation_id / description
      Added value: +"Target presentation ID."
    • changedInput schema / properties / text / description
      Previous value: -"Initial text content."New value: +"Initial text content for the box."
    • addedInput schema / properties / top / description
      Added value: +"Y offset from top in EMU. Default 914400 (1 in)."
    • addedInput schema / properties / user_google_email / description
      Added value: +"The user's Google email address (authenticated\naccount)."
    • addedInput schema / properties / width / description
      Added value: +"Box width in EMU. Default 3000000 (≈3.28 in)."
  2. First observedv1.19.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses behavior (adds text box, positions in EMU, requires OAuth scope) but lacks details on potential side effects, error cases, or limits (e.g., max text length). Still, it covers key behavioral traits sufficiently.

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?

Concise at 5 sentences, front-loaded with purpose and alternatives, then units and auth. Every sentence adds value with no redundancy or filler.

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?

Given 11 parameters, no annotations, and existing output schema, the description is fairly complete. It covers purpose, usage guidelines, units, and auth. Lacks details on behavior when optional parameters are omitted or output format, but schema and output schema compensate. Good overall.

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 descriptions for each parameter. Description adds context about EMU units and OAuth scope but does not enrich individual parameter meanings. Baseline of 3 is appropriate since schema already does the heavy lifting.

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 'Add a text box to a slide with initial content and position' and distinguishes from sibling tools (create_slides_shape for shapes, batch_update_presentation for editing existing text). The verb+resource combination is specific and unambiguous.

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 tells when to use this tool (for text content), and when to use alternatives (create_slides_shape for geometric shapes, batch_update_presentation for editing existing text). Provides clear context and exclusions.

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