ConvertAPI

Dynamic ConvertAPI call with OpenAPI-driven parameter validation. RECOMMENDED WORKFLOW: 1. First, call 'GetConversionParameters' to discover supported parameters for your specific fromFormat->toFormat conversion 2. Review the available parameters, their types, constraints, and descriptions 3. Then call this 'convert' tool with your chosen parameters This tool supports all parameters from the live OpenAPI specification including PageSize, PageOrientation, File, StoreFile, Quality, etc. Parameters are validated against the current schema before conversions. REQUIRED PARAMETERS: - fromFormat: Source format (e.g., 'docx', 'xlsx', 'jpg') - toFormat: Target format (e.g., 'pdf', 'png', 'html') EXAMPLE USAGE: First check: get_conversion_parameters(fromFormat='pdf', toFormat='jpg') Then convert: convert(fromFormat='pdf', toFormat='jpg', parameters={'PageRange':'1-3', 'ImageResolution':'300'}) SOURCE FILE HANDLING — pick the first option that applies: 1. The user attached the file to this conversation: pass it in the top-level 'file' argument. Do not put it in 'parameters'. Nothing needs uploading first. 2. The file is already a public URL: pass it as parameters={'File':'<url>'}. 3. You have a ConvertAPI FileId (e.g. from an upload tool): pass it as parameters={'File':'<FileId>'}. 4. The file only exists in your sandbox and you can run shell commands: call 'request_upload_url' first to get a FileId, then use option 3. Never pass a local or sandbox path (e.g. '/mnt/data/report.pdf') as 'File' — it is not reachable from ConvertAPI. RESULT HANDLING (IMPORTANT): The result is returned as one or more ResourceLink content blocks pointing at ConvertAPI-hosted URLs. Do NOT fetch these URLs yourself with your bash, code-execution, or web tools — they are intended for the end user to download via the rendered link in the chat. Just summarize that the conversion succeeded; do not read the file content.

convert

Retrieves a list of available converters that match the specified tags.

get_converters_by_tags

Get all available parameters with their descriptions and constraints for a specific conversion. CALL THIS FIRST before using the 'convert' tool to understand which parameters are supported and their requirements. Returns detailed information about: - Parameter names - Data types (string, integer, boolean, etc.) - Allowed values and constraints - Parameter descriptions - Whether parameters are required or optional This helps you construct valid conversion requests with appropriate parameters. If the user has a local file (not a public URL), obtain a FileId first via 'request_upload_url'; then pass it as the 'File' parameter to 'convert'.

get_conversion_parameters

Get a curl command that uploads a local file directly to ConvertAPI and returns a FileId. Use this when the user has attached a file to the conversation or it exists in your sandbox. Do NOT use this for files already reachable via a public URL — for URLs, pass them straight to 'convert' as parameters={'File':'<url>'}. Steps: 1. Call this tool with the file's path in your sandbox (e.g. '/mnt/user-data/uploads/report.docx') or just its name if it is in the current working directory. 2. Execute the returned 'curl' command yourself using your bash / code-execution tool. Do not ask the user to run it manually. 3. The curl response is a JSON body containing a 'FileId', e.g. {"FileId":"abc123","FileName":"report.docx","FileExt":"docx"}. Parse it. 4. Call the 'convert' tool with parameters that include the FileId, e.g. parameters={'File':'abc123'}. Notes: - The upload itself is unauthenticated; the subsequent 'convert' call enforces the user's authentication. - Uploaded files are retained on ConvertAPI for ~3 hours.

request_upload_url

Searches for available converters that match the specified search terms.

search_converters