PDFMakerAPI
Server Details
Turn a description into a shareable, editable PDF — invoices, certificates, reports, resumes.
- 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.2/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, naming is trivially consistent and follows a clear verb_noun pattern (create_document).
A single tool for an entire PDF maker API feels minimal; while the tool is comprehensive, one might expect additional tools for document management or template operations.
The tool covers document creation but lacks operations like listing, updating, or deleting documents, which are notable gaps for a full PDF service.
Available Tools
1 toolcreate_documentAInspect
Create a professional, shareable PDF document — invoices, receipts, certificates, reports, resumes, letters. Returns a link that opens the document in the PDFMakerAPI editor to preview, edit any field, and download the PDF.
Design a THOROUGH, realistic document (don't leave it sparse) that exactly follows this model, then pass it as document.
DOCUMENT MODEL (PDFMakerAPI) Document: { id, name, description, pageSize ("letter"|"a4"|"legal"|"letter-landscape"|"a4-landscape"|"square", default "a4"), pageBackgroundColor (hex), margin ("none"|"sm"|"md"|"lg", default "lg"), gap ("none"|"sm"|"md"|"lg", default "lg"), variables: Variable[], children: Node[] } Variable: { id, name (snake_case, used as {{name}}), label, type ("text"|"date"|"number"|"currency"), defaultValue? } Node (each has id, name, width ("full"|"1/2"|"1/3"|"1/4"|"2/3"|"3/4"|"auto"), order, align? ("left"|"center"|"right"), style?):
container: { type:"container", layout:{ direction:"row"|"column", gap, justify?, alignItems? }, children: Node[] }
text: { type:"text", content (supports \n and {{vars}}), fontSize? ("xs"|"sm"|"base"|"lg"|"xl"), fontWeight? ("normal"|"medium"|"semibold"|"bold") }
table: { type:"table", columns: { id, name (data key), label, width?, align? }[], rowVariable: string }
spacer: { type:"spacer", height:"sm"|"md"|"lg"|"xl" }
divider: { type:"divider", lineStyle?:"solid"|"dashed"|"dotted" }
RULES
In text, insert values with {{snake_case_name}}; every {{name}} MUST be declared in variables[] with a realistic defaultValue.
Tables do NOT use {{}}: a table renders one row per item in its rowVariable array, pulling item[column.name]; the rowVariable variable's defaultValue must be a JSON-encoded string of the row array.
For label/value pairs, nest a direction:"row" container with a BOLD label (fontWeight:"bold") + the {{variable}} value, each with a width (e.g. "1/3" / "2/3").
Spacing between top-level sections comes from the document "gap" (default "lg") — don't add spacers between sections.
Right-align money/number columns; every id unique. Keep it clean and professional.
After the tool returns a url, share it and tell the user they can open it to preview, edit any field, and download the PDF.
| Name | Required | Description | Default |
|---|---|---|---|
| document | Yes | The PDFMakerAPI Document object to create, following the schema in this description. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must bear the full burden. It does not explicitly state behavioral aspects like whether it is a mutation, error handling, or performance characteristics. However, the name 'create' implies creation, and the focus is on the input format rather than side effects.
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 very long and includes a full API reference, which is not concise. While the detail is necessary for such a complex parameter, it could be better structured (e.g., bullet points, clearer sections) to improve readability.
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 complexity of the document parameter with nested objects and many fields, the description is extremely complete. It covers all aspects of the input, including rules, defaults, and examples, and even mentions the return value (a URL to the editor).
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?
The input schema is extremely generic (just an object property with no defined structure), but the description provides an exhaustive and detailed schema for the document parameter, including all fields, types, defaults, and rules. This adds immense value beyond the schema's minimal description.
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 identifies the tool's purpose: creating a professional, shareable PDF document like invoices, receipts, etc. It uses specific verbs and resource, distinguishing it from any potential sibling tools.
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 implies when to use this tool (to create PDF documents following the PDFMakerAPI model), but it does not explicitly exclude alternative tools due to no siblings. The context is clear and provides guidance on what the tool produces.
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!