MCP Examples - DeckFlow Developers

These examples are written as product documentation drafts. Tool names and parameters are placeholders until the final MCP schema is confirmed.

Create A Deck From Research Material

User prompt:

Use DeckFlow to turn this research PDF into a 12-slide investor-ready deck.
Keep technical charts readable, use a concise executive tone, and export PPTX.

Expected agent flow:

Confirm the attached file is a supported Create source.
Call create_deck with the source file, requested slide count, audience, tone, and PPTX output.
Poll get_task until the task completes.
Return the PPTX temporary download link and mention any warnings, such as missing fonts or chart fidelity issues.

Parameters the user or agent should provide:

Parameter	Example
`source_type`	`file`
`source`	Attached PDF
`slide_count`	`12`
`audience`	`investors`
`tone`	`executive, concise`
`output_format`	`pptx`

Create A Deck From A URL

User prompt:

Create a short product overview deck from this URL and export both PPTX and PDF.

Expected agent flow:

Check whether URL import is supported.
Call create_deck with source_type=url.
Request multiple output formats if supported, or run export after creation.
Return both temporary download links.

Parameters still to define:

Parameter	Open Question
`source_url`	Are public URLs only supported, or can authenticated pages be imported?
`output_format`	Can one task return multiple formats?
`crawl_depth`	Is URL import limited to one page or can it follow links?

Revamp An Existing Deck

User prompt:

Use DeckFlow to revamp this PPTX with our saved Brand DNA.
Do not rewrite the content. Keep the final output editable.

Expected agent flow:

Call list_brand_profiles if the user does not specify a Brand DNA profile.
Call revamp_deck with the selected brand profile and preserve_content=true.
Poll task status.
Return the editable output file as a temporary download link.

Parameters the user or agent should provide:

Parameter	Example
`file`	Attached PPTX
`style_mode`	`brand_dna`
`brand_profile_id`	Selected profile
`preserve_content`	`true`
`output_format`	`pptx`

Translate Without Breaking Layout

User prompt:

Translate this Keynote deck into Japanese.
Keep the layout intact and use our product glossary.

Expected agent flow:

Validate that Keynote input is supported.
Call list_glossaries if the user does not name a glossary ID.
Call translate_deck with target language and glossary.
Poll until complete.
Return the translated file as a temporary download link, along with any layout warnings.

Parameters the user or agent should provide:

Parameter	Example
`file`	Attached Keynote file
`target_language`	`ja`
`glossary_id`	Selected glossary
`preserve_layout`	`true`
`output_format`	Same as input, if supported

Convert HTML To PPTX

User prompt:

Use DeckFlow to convert this HTML page into an editable PowerPoint deck.

Expected agent flow:

Use convert_file with operation=html_to_pptx.
Pass either uploaded HTML or pasted HTML content.
Return the generated PPTX as a temporary download link.

Parameters the user or agent should provide:

Parameter	Example
`operation`	`html_to_pptx`
`file` or `content`	HTML file or pasted HTML
`output_format`	`pptx`

Extract Text Shapes From PPTX

User prompt:

Extract all text boxes from slides 3 through 10 of this PPTX and return structured JSON.

Expected agent flow:

Call extract_file_content with operation=pptx_text_extractor.
Set page_range or slide_range to slides 3 through 10.
Request structured output.
Return JSON or a downloadable JSON file.

Parameters still to define:

Parameter	Open Question
`page_range` vs `slide_range`	Which name should the API/MCP use consistently?
`include_coordinates`	Should shape positions be returned by default?
`output_format`	Inline JSON response or generated JSON file?

Merge Several PPTX Files

User prompt:

Merge these three PPTX files in the order uploaded.
Keep each deck's original formatting as much as possible.

Expected agent flow:

Preserve the upload order or ask the user to confirm ordering.
Call compose_files with operation=pptx_merge.
Poll until complete.
Return the merged deck as a temporary download link.

Parameters the user or agent should provide:

Parameter	Example
`operation`	`pptx_merge`
`files`	Ordered PPTX file references
`preserve_styles`	`true`
`output_name`	Optional filename

Compress A Delivery Package

User prompt:

Compress this PPTX so I can email it, but keep image quality high.

Expected agent flow:

Call optimize_file with operation=file_compress.
Choose a conservative compression preset.
Return the compressed file as a temporary download link, plus before/after size if available.

Parameters still to define:

Parameter	Open Question
`quality`	Preset enum or numeric value?
`target_size_mb`	Should the user be able to request a max size?
`size_report`	Should the result include before/after byte size?

Agent Behavior Guidelines

Agents should ask a follow-up question when:

The source file is missing.
The user requests a Brand DNA profile, template, or glossary but has not specified which one and no default exists.
The output format is unsupported or ambiguous.
The task could overwrite or delete an existing workspace asset.
Multiple files are attached and ordering matters.

Agents should proceed without extra questions when:

The user attached exactly one compatible file.
The requested operation and output format are clear.
DeckFlow capabilities can be discovered through get_deckflow_capabilities.
Sensible defaults are defined by the final schema.

Example Capability Discovery Prompt

Use DeckFlow MCP to inspect available capabilities, then tell me which operations support PPTX input and which output formats each one can produce.

Expected agent flow:

Call get_deckflow_capabilities.
Filter capabilities where input formats include PPTX.
Summarize supported outputs and limits.