DeckExtract
Server Details
Download DocSend and Papermark decks as PDF or PPTX, including email-gated and protected links.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 1 of 1 tools scored.
Only one tool exists, so there is no ambiguity between tools. The sole tool has a clear purpose.
With only one tool, naming consistency is inherently perfect. The single name 'deckextract' is a compound word that clearly indicates its function.
The server has exactly one tool, which is appropriate for its focused purpose of extracting decks from sharing links. While the count is on the low end, it covers the core functionality without unnecessary bloat.
The tool fully covers the stated purpose: extracting a deck and providing a download link. There are no obvious gaps for this single-operation server.
Available Tools
1 tooldeckextractExtract a DocSend or Papermark deckAInspect
Extract a deck from a DocSend or Papermark sharing link and get a download URL for the PDF or PPTX (link valid for about an hour). Typical extraction takes 15-90 seconds; the public API is rate limited to 5 extractions per IP per 30 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The deck sharing link, e.g. https://docsend.com/view/... or https://papermark.com/view/... | |
| No | Email to present to email-gated decks. If omitted, an ephemeral address is generated automatically when the deck requires one. | ||
| format | No | Output format (default 'pdf') | |
| password | No | Passcode for passcode-protected decks |
Output Schema
| Name | Required | Description |
|---|---|---|
| format | Yes | |
| expiresAt | Yes | ISO timestamp when the URL expires |
| sizeBytes | Yes | |
| sourceUrl | Yes | |
| downloadUrl | Yes | Temporary URL of the extracted deck |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false, destructiveHint=false, etc. The description adds valuable behavioral details beyond annotations: typical extraction time, rate limits, and that the download URL is valid for about an hour. No contradictions.
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?
The description is two sentences long, front-loaded with the main purpose, and contains no extraneous information. Every sentence adds value.
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?
Given the presence of a full output schema (as indicated) and detailed annotations, the description adequately covers purpose, usage, behavior, and constraints (time, rate limits). It is complete for agent invocation.
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 coverage is 100%, so baseline is 3. The description does not add significant meaning beyond the schema; it only mentions the link types and output format. The schema already provides detailed parameter descriptions.
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 clearly specifies the action ('extract'), the resources ('DocSend or Papermark deck'), and the output ('download URL for PDF or PPTX'). It is specific and leaves no ambiguity about the tool's function.
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?
The description provides context on when to use (having a sharing link), typical execution time (15-90 seconds), and rate limits (5 per IP per 30 minutes). It does not explicitly mention alternatives or when not to use, but no sibling tools exist, so guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!