Skip to main content
Glama
Hermoso

Hermoso

Official

Swipefile to Google Slides

export_swipefile_deck

Export a swipefile collection into a new Google Slides deck with one slide per saved ad showing the creative, brand, ad copy, run dates and platform. Returns the presentation ID and URL.

Instructions

Turn a SWIPEFILE COLLECTION into a real Google Slides deck — one slide per saved ad, carrying the creative, the brand, the ad copy, the run dates with the run length, and the platform. This is the thing a marketer actually presents to a client or a team. Returns the presentation id + URL. Creates a NEW deck every time: under the drive.file scope Hermoso can only touch files it created, so it cannot add slides to a deck the user already has. A creative whose ad-library link has expired cannot be embedded — Meta signs those URLs with a short expiry — so that slide says so in words and keeps its copy and run dates, and the reply reports how many. Needs Google Drive connected (Connectors > Google Drive — one connection covers Drive, Sheets, Docs and Slides).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_swipefile_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax ads to include, 1-60 (default 30)
titleNodeck title (default: the collection name)
collectionNothe swipefile collection to export, by name or id (default: the first collection)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that every call creates a new deck, why it cannot append to existing decks under drive.file scope, how expired ad-library links are handled, what the reply reports, and what connection is required. These are meaningful behavioral details that an agent would not get from the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the key limitations are stated directly. The sentence about this being 'the thing a marketer actually presents' adds useful context but is slightly promotional, and the overall description is on the longer side for a three-parameter tool.

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?

For a non-idempotent, open-world export tool without an output schema, the description covers what is produced, how failures are represented, what dependency is required, and the append limitation. An agent has enough information to call the tool correctly and understand its side effects.

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%, so the schema already documents collection, title, and limit with defaults. The description mentions the collection and the one-slide-per-ad structure but does not add further syntax, constraints, or meaning for the individual parameters. This is the expected baseline when the schema carries the parameter detail.

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 states a specific verb and resource: turn a swipefile collection into a Google Slides deck with one slide per saved ad. It also clarifies the output and distinguishes the tool from append/save style siblings by stressing that it creates a new deck every time and cannot add to an existing one.

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 gives a clear usage context ('what a marketer actually presents to a client or a team') and a key prerequisite ('Needs Google Drive connected'). It also implicitly rules out using this tool to extend an existing deck. It does not explicitly name an alternative tool for that case, which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools