Slidler
Server Details
Turn a URL, YouTube video or text into a branded LinkedIn/Instagram carousel PDF. No key needed.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another tool. Its purpose is clearly stated as creating a carousel and temporary PDF.
The single tool follows a clear verb_noun convention (create_carousel). There are no other names to create inconsistency.
A single tool is very thin for a server named Slidler, even if create is the core operation. Users likely need at least list, get, or delete operations to manage carousels/PDFs.
The surface only covers creation of a carousel and temporary PDF. There are no tools for retrieving, listing, updating, or deleting outputs, which leaves significant lifecycle gaps.
Available Tools
1 toolcreate_carouselBInspect
Create a branded carousel and temporary PDF from a public URL or text.
| Name | Required | Description | Default |
|---|---|---|---|
| n | No | Signed decimal integer n is clamped to 6..8; non-integer n defaults to 6. The response reports effective n. | |
| title | No | Optional title, allowed only with text. | |
| source | Yes | Source text; at least 40 printable non-whitespace characters. Or a public HTTP(S) URL. Text cap: 1800 UTF-8 bytes; URL cap: 2048 UTF-8 bytes. |
Output Schema
| Name | Required | Description |
|---|---|---|
| n | Yes | |
| Yes | ||
| kind | Yes | |
| title | Yes | |
| slides | Yes | |
| warnings | Yes | |
| page_count | Yes | |
| api_version | Yes | |
| point_count | Yes | |
| caption_status | Yes | |
| renderer_version | Yes |
TDQS
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 says 'temporary PDF' which hints at ephemeral output, but doesn't explain permissions needed, rate limits, what 'branded' means, or what happens to the PDF afterward. Significant gaps for a creation tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, efficient sentence that front-loads the action and output. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is moderately complex (creation with constraints, temporary artifact), has no annotations, and has an output schema (so return values needn't be explained). The description covers the basic operation but omits behavioral context like auth requirements, what 'branded' entails, or the lifecycle of the temporary PDF.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all three parameters including constraints on 'n', 'title', and 'source'. The description adds no parameter details beyond what the schema provides, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb (create) and resource (branded carousel and temporary PDF) with a named input source. It's specific about what gets produced but doesn't distinguish from any alternatives (none provided as siblings).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, no prerequisites mentioned, and no exclusions. The description merely states what it does, leaving the agent to infer when it's appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
create_carousel
Related MCP Connectors
Turn notes, articles and ideas into LinkedIn carousels in your brand, then export or schedule them.
- CanvoraOAuthai.canvora
Turn any idea, URL, doc, or PDF into on-brand visuals: 100+ formats, native in 150+ languages
Turn any URL or text into Twitter threads, LinkedIn posts, Instagram captions, YouTube titles and…
Clone viral TikTok/Instagram slideshows for your business. Async; 6 tools; Bearer API key.
Related MCP Servers
- AlicenseAqualityAmaintenanceTurn idead and markdown into branded, multi-page social carousels and slideshows for TikTok, LinkedIn, Instagram, Threads and Xiaohongshu.37MIT
- AlicenseAqualityCmaintenanceConvert HTML to PDF/PNG/WebP/PPTX slide carousels with 11 themes. For LinkedIn carousels, decks, Instagram posts, and infographics — Puppeteer-based pixel-perfect rendering.62MIT
- AlicenseAqualityDmaintenanceMCP server that turns articles, transcripts, and markdown into LinkedIn carousel PDFs, Instagram PNGs, and Threads PNGs. Content in, slides out. No web UI, no cloud service.53MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate finished TikTok/Instagram carousels from a topic or video, then refine them layer by layer with text, styling, photo and slide operations. Exports the results as 1080×1920 PNG slides plus layered PSD and SVG files for Photoshop, Photopea and Figma.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.