Skip to main content
Glama

convert-contents

Convert documents between formats like Markdown, HTML, PDF, and DOCX. Specify content, output format, and complete file paths for advanced formats to transform and save files.

Instructions

Converts content between different formats. Transforms input content from any supported format into the specified output format.

🚨 CRITICAL REQUIREMENTS - PLEASE READ:

  1. PDF Conversion:

    • You MUST install TeX Live BEFORE attempting PDF conversion:

    • Ubuntu/Debian: sudo apt-get install texlive-xetex

    • macOS: brew install texlive

    • Windows: Install MiKTeX or TeX Live from https://miktex.org/ or https://tug.org/texlive/

    • PDF conversion will FAIL without this installation

  2. File Paths - EXPLICIT REQUIREMENTS:

    • When asked to save or convert to a file, you MUST provide:

      • Complete directory path

      • Filename

      • File extension

    • Example request: 'Write a story and save as PDF'

    • You MUST specify: '/path/to/story.pdf' or 'C:\Documents\story.pdf'

    • The tool will NOT automatically generate filenames or extensions

  3. File Location After Conversion:

    • After successful conversion, the tool will display the exact path where the file is saved

    • Look for message: 'Content successfully converted and saved to: [file_path]'

    • You can find your converted file at the specified location

    • If no path is specified, files may be saved in system temp directory (/tmp/ on Unix systems)

    • For better control, always provide explicit output file paths

Supported formats:

  • Basic formats: txt, html, markdown

  • Advanced formats (REQUIRE complete file paths): pdf, docx, rst, latex, epub

āœ… CORRECT Usage Examples:

  1. 'Convert this text to HTML' (basic conversion)

    • Tool will show converted content

  2. 'Save this text as PDF at /documents/story.pdf'

    • Correct: specifies path + filename + extension

    • Tool will show: 'Content successfully converted and saved to: /documents/story.pdf'

āŒ INCORRECT Usage Examples:

  1. 'Save this as PDF in /documents/'

    • Missing filename and extension

  2. 'Convert to PDF'

    • Missing complete file path

When requesting conversion, ALWAYS specify:

  1. The content or input file

  2. The desired output format

  3. For advanced formats: complete output path + filename + extension Example: 'Convert this markdown to PDF and save as /path/to/output.pdf'

Note: After conversion, always check the success message for the exact file location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentsNoThe content to be converted (required if input_file not provided)
input_fileNoComplete path to input file including filename and extension (e.g., '/path/to/input.md')
input_formatNoSource format of the content (defaults to markdown)markdown
output_formatNoDesired output format (defaults to markdown)markdown
output_fileNoComplete path where to save the output including filename and extension (required for pdf, docx, rst, latex, epub formats)
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes behavioral traits such as installation prerequisites for PDF conversion, file path requirements, file location after conversion (e.g., saved in system temp directory if no path specified), and success message details. This covers critical operational aspects beyond basic functionality.

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

Conciseness3/5

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

The description is front-loaded with a clear purpose but includes extensive bullet points and examples, making it lengthy. While all information is relevant, it could be more streamlined; some details like installation steps and repetitive examples add bulk without always being concise. It earns its place but lacks optimal brevity.

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 the complexity (5 parameters, no output schema, no annotations), the description is highly complete. It covers purpose, usage guidelines, behavioral traits, parameter requirements, examples, and post-conversion actions. It compensates well for the lack of structured data, ensuring the agent has all necessary context to use the tool correctly.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds significant value by explaining parameter semantics beyond the schema, such as the necessity of complete file paths for output_file in advanced formats, examples of usage, and clarification on when parameters are required (e.g., output_file for pdf, docx, etc.). However, it doesn't deeply elaborate on all parameter interactions beyond what's implied in the guidelines.

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's purpose as converting content between different formats, specifying it transforms input content from any supported format into a specified output format. It distinguishes between basic and advanced formats, providing specific examples like txt, html, markdown, pdf, docx, etc., making the verb+resource explicit and comprehensive.

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?

The description provides explicit usage guidelines, including critical requirements for PDF conversion (e.g., installing TeX Live), file path specifications (complete directory path, filename, extension), and when to use certain parameters. It offers correct and incorrect usage examples, specifies requirements for advanced formats, and details what to check after conversion, covering when/when-not scenarios thoroughly.

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/jathinkolla/pandoc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server