Skip to main content
Glama
pictify-io

Pictify MCP Server

by pictify-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pictify_render_pdf

Generate PDF documents from templates with variable data for invoices, certificates, receipts, contracts, and reports. Programmatically create professional documents by substituting template variables with your data.

Instructions

Generate a single-page PDF from a saved template with variable substitutions. Common use cases: invoices, certificates, receipts, contracts, reports, event tickets, shipping labels, and any document that needs to be generated programmatically. WORKFLOW: Call pictify_get_template_variables first to discover available variables and their types, then call this tool with the appropriate variable values. Supports standard page sizes (A4, Letter, Legal, etc.) — use pictify_list_pdf_presets to see all options. Returns the hosted PDF URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateIdYesThe template UID to render as a PDF. Use pictify_list_templates to find available templates.
variablesNoTemplate variables as key-value pairs (e.g., { title: 'Invoice #001', amount: '$1,000', date: '2024-03-09' }). Use pictify_get_template_variables to discover available variable names and types.
presetNoPDF page size preset (e.g., 'A4', 'Letter', 'Legal'). Use pictify_list_pdf_presets to see all available presets with their dimensions. If not specified, uses the template's default dimensions.
titleNoPDF document title metadata — appears in the browser tab when the PDF is opened

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses it returns a hosted PDF URL and that it's single-page. However, it lacks details on side effects, error handling, or permission requirements. The description is adequate but not rich in behavioral context.

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: purpose first, then common use cases, then step-by-step workflow. Every sentence adds value; no redundancy. Length is appropriate for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Describes input (template, variables, preset), workflow, and output (hosted PDF URL). Missing details about error conditions or validation. For a single-purpose generation tool, it covers the essential context adequately.

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. Description adds value by explaining the workflow for variables (use get_template_variables) and preset (use list_pdf_presets). This goes beyond schema descriptions, providing strategic guidance.

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?

Description clearly states it generates a single-page PDF from a saved template with variable substitutions, listing common use cases. It explicitly differentiates from siblings by specifying 'single-page' (contrast with pictify_render_multi_page_pdf) and mentions batch rendering alternatives.

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?

Provides explicit workflow: call pictify_get_template_variables first to discover variables, then use this tool. Also advises using pictify_list_pdf_presets for page size options. Does not explicitly state when not to use or alternatives, but the workflow is clear.

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