Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Convert a OneDrive file to PDF or JPG

convert_onedrive_file

Convert OneDrive files in 130+ formats — PSD, AI, Word, Excel, raw camera, video — to PDF or JPG using Microsoft's servers, returning a durable URL you can render or post.

Instructions

Turn a file already in the user’s OneDrive into a PDF or a JPG — Microsoft does the conversion on its own servers, so nothing is re-encoded here and nothing is lost in a screenshot. It reads about 130 source formats, which is the point: PowerPoint and Word decks, Excel, Photoshop PSD, Illustrator AI, Sketch, 3D (fbx/glb/obj), video (mp4/mov/webm), HEIC from an iPhone, and the raw camera formats (CR2, NEF, ARW, DNG) that nothing else in this product can open. Use it to turn a client’s deck into images you can actually put in an ad, to get a usable JPG out of a designer’s PSD or a photographer’s raw file, or to hand someone a PDF of a spreadsheet. CONVERTING TO JPG REQUIRES BOTH width AND height — Microsoft refuses the call without them. The result is stored at a durable Hermoso URL you can pass straight to a render or a post; Microsoft’s own conversion link expires within minutes, so do not hand that one to anyone. Needs OneDrive connected — no new permission.

Input Schema

NameRequiredDescriptionDefault
widthNoREQUIRED for jpg — output width in pixels
fileIdYesthe OneDrive item id, from list_onedrive_files
formatNodefault pdf
heightNoREQUIRED for jpg — output height in pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: conversion happens on Microsoft's servers with no local re-encoding, JPG requires both width and height or Microsoft rejects the call, and the returned URL is durable while Microsoft's own link expires in minutes. This is exactly the operational detail an agent needs and cannot get from readOnlyHint/destructiveHint alone; nothing contradicts the annotations.

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?

Front-loads the core action and the JPG constraint is capitalized and easy to spot. Some enumeration of formats and ad-copy flourishes ('hand someone a PDF of a spreadsheet') run long, but they carry real capability information rather than filler.

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 no output schema, the description correctly fills the gap by describing the return value (a durable Hermoso URL usable in a render or post) and warns against the expiring Microsoft link. Prerequisites, the conditional parameter rule, and format support are all covered.

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 100%, so baseline is 3; the description goes one step further by explaining *why* width and height matter (Microsoft refuses the call without both), which reinforces the hard conditional requirement rather than merely restating it. It says little extra about fileId or the format default beyond the 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?

States a specific verb and resource (turn a OneDrive file into PDF or JPG) and immediately scopes it to files already in OneDrive, which distinguishes it from upload/import siblings like save_to_onedrive and get_onedrive_file. The list of supported source formats makes the tool's capability unmistakable.

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?

Gives concrete when-to-use scenarios (client deck to ad images, PSD/raw to JPG, spreadsheet to PDF) and names the prerequisite (OneDrive connected, no new permission). The 'nothing else in this product can open' framing implicitly routes raw/PSD/AI cases here rather than to generate_image or edit_image.

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