Eledo PDF

@eledo-pdf list all my templates and show me which ones are most recently updated

Found 7 templates in your Eledo account: 1. **Invoice_2024** (ID: tpl_inv2024) — last updated 3 days ago 2. **Contract_Standard** (ID: tpl_contract_std) — last updated 1 week ago 3. **Report_Monthly** (ID: tpl_rpt_monthly) — last updated 2 weeks ago 4. **Certificate_Completion** (ID: tpl_cert) — last updated 3 weeks ago 5. **Quote_Template** (ID: tpl_quote) — last updated 1 month ago 6. **NDA_Basic** (ID: tpl_nda) — last updated 2 months ago 7. **Proposal_Draft** (ID: tpl_proposal) — last updated 3 months ago This is an illustrative example showing how the MCP surfaces your template library with recency context.

This example demonstrates read-only template discovery. The List Templates tool intentionally excludes Eledo's public template library to avoid unbounded results. Useful for auditing what's available before generating documents.

@eledo-pdf get the schema for my Invoice_2024 template so I know what fields I need to fill

The **Invoice_2024** template (tpl_inv2024) expects these input fields: - `customer_name` (string, required) - `customer_address` (string, required) - `invoice_number` (string, required) - `invoice_date` (date, required, format: YYYY-MM-DD) - `line_items` (array of objects, required) - Each item: `description` (string), `quantity` (number), `unit_price` (number) - `tax_rate` (number, optional, default: 0) - `notes` (string, optional) This illustrative schema shows the structure Eledo expects. Validate your data against this before calling Generate PDF.

Critical pre-flight step before document generation. The Get Template Schema tool prevents quota waste by surfacing required fields and data types upfront. Missing or invalid fields cause Eledo to render incomplete PDFs while still consuming quota.

@eledo-pdf generate an invoice using Invoice_2024 with customer Acme Corp, invoice #2024-089, dated today, one line item for consulting services at $5000

Generated PDF successfully. Document details: - **Template**: Invoice_2024 (tpl_inv2024) - **Customer**: Acme Corp - **Invoice**: #2024-089 - **Date**: 2024-01-15 - **Line item**: Consulting Services × 1 @ $5,000.00 - **Total**: $5,000.00 - **Download URL**: `https://eledo.io/downloads/doc_abc123xyz.pdf` (expires in 24 hours) This illustrative example shows a successful generation. **Important**: This call consumed 1 document from your Eledo quota. The download link is temporary.

This write action consumes quota immediately, even if the PDF has errors. Always validate input data with Get Template Schema first. The download URL expires quickly (typically 24 hours), so retrieve the file promptly or store it elsewhere for long-term access.

When Eledo wins for recurring document workflows with fixed schemas

A 6-person sales team closes 20-30 deals a month and needs MSAs, SOWs, and order forms generated from CRM data without touching Google Docs. Eledo PDF is the right call if your documents follow a stable template structure and you're willing to maintain those templates in Eledo's editor. The MCP's Get Template Schema tool lets the AI validate input fields before generation, so you catch missing customer names or PO numbers before burning quota. The trade-off: each PDF costs a document credit, so high-volume scenarios (like generating 500 invoices nightly) get expensive fast. If your team closes fewer than 100 deals a month and the templates change quarterly or less, Eledo keeps contract generation in the AI loop without custom code.

Where Eledo falls short for multi-source document stitching

A 3-person customer success team wants to generate personalized onboarding packets—welcome letter, setup guide, account summary—by pulling data from Stripe, Notion, and the CRM. Eledo PDF isn't the move here. The MCP only generates from Eledo's own templates, so you'd need to pre-format all source data into the exact schema each template expects, then make separate API calls per document. There's no native way to merge PDFs or pull live data from other tools during generation. If your onboarding flow requires stitching content from multiple systems or conditional sections based on plan tier, you're better off with a general-purpose PDF library or a document automation platform that handles data connectors. Eledo shines when the data is already structured and the template is the single source of layout truth.

When Eledo works for low-frequency, high-polish reporting

A 10-person ops team sends a weekly board deck—metrics dashboard, narrative summary, appendix tables—to five executives every Monday morning. Eledo PDF is a solid fit if the report layout is fixed and the data comes from a single source (like a database or analytics API) that the AI can query and format. The List Templates and Get Template Schema tools let the AI pick the right template version and validate the data structure before generation, so you avoid broken charts or missing tables. The constraint: if your report needs conditional sections (show revenue breakdown only if growth is above 10%) or real-time data refresh during the PDF render, Eledo's static template model gets clunky. For a weekly cadence with predictable structure, though, the quota cost is manageable and the output quality beats cobbling together charts in a Google Doc.