Skip to main content
Glama

create_slides_shape

Insert shapes like rectangles and arrows into Google Slides. Specify type, position, size, and fill color to build diagrams and layouts programmatically.

Instructions

Create a new shape element (rectangle, ellipse, arrow, etc.) on a Google Slide.

Use this to build layouts programmatically — callouts, diagrams, backgrounds. For a TEXT-focused box, use create_slides_text_box (simpler + auto-sized for text). For styling an EXISTING shape (outline, shadow, filled color), use style_slides_shape. To add text inside a shape after creation, use batch_update_presentation with insertText.

Requires OAuth scope: https://www.googleapis.com/auth/presentations (write). Creates exactly one shape per call. Returns the new shape's object ID so you can reference it in follow-up calls (inserting text, setting fill, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
page_object_idYesObject ID of the slide where the shape will be placed. Get it from `get_presentation.slides[].objectId` or `get_page`.
shape_typeYesShape enum from Google's API. Common values: `RECTANGLE`, `ROUND_RECTANGLE`, `ELLIPSE`, `TRIANGLE`, `RIGHT_TRIANGLE`, `DIAMOND`, `PENTAGON`, `HEXAGON`, `OCTAGON`, `PARALLELOGRAM`, `TRAPEZOID`, `STAR_5`, `STAR_6`, `STAR_8`, `STAR_12`, `STAR_16`, `STAR_24`, `STAR_32`, `ARROW_RIGHT`, `ARROW_LEFT`, `ARROW_UP`, `ARROW_DOWN`, `LEFT_RIGHT_ARROW`, `CLOUD`, `SUN`, `MOON`, `HEART`, `LIGHTNING_BOLT`, `SPEECH`, `CLOUD_CALLOUT`. Full list: https://developers.google.com/slides/api/reference/rest/v1/pages/pageElements#Type
leftNoX position (top-left corner) in EMUs (English Metric Units). Default `914400` EMU = 1 inch from the slide's left edge. Conversion: 1 inch = 914,400 EMU; 1 point = 12,700 EMU; 1 cm = 360,000 EMU.
topNoY position (top-left corner) in EMUs. Default `914400` = 1 inch down.
widthNoShape width in EMUs. Default `2000000` ≈ 2.19 inches.
heightNoShape height in EMUs. Default `2000000` ≈ 2.19 inches.
fill_colorNoOptional hex color for the shape interior, e.g., `#4285F4`. Accepts `#RRGGBB` or `RRGGBB`. Omit for the default transparent fill (shape renders as an outline only until you set a fill later).

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 description carries full burden. Details OAuth scope, creates exactly one shape per call, returns object ID, and explains transparent fill behavior. Could add more about error cases but sufficient.

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?

Well-structured, front-loaded with purpose, bullet points for alternatives, and clear notes. Every sentence adds value without redundancy.

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 complexity (9 params, 4 required) and presence of output schema, description covers behavior, usage, parameters, and return value. No gaps identified.

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?

Schema description coverage is 89% (baseline 3). Description adds significant value: explains shape_type with common values and link, EMU units for position/size, and fill_color optionality. Exceeds baseline.

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 it creates a shape element (rectangle, ellipse, etc.) on a Google Slide. Distinguishes from sibling tools like create_slides_text_box 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?

Explicitly says when to use (build layouts programmatically) and when not (use create_slides_text_box for text, style_slides_shape for styling). Also mentions follow-up actions like adding text via batch_update_presentation.

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