RemplirPDF MCP server

Obtenir un lien de téléchargement

get_download_link

Read-onlyIdempotent

Generate a fresh 24-hour PDF download link and in-app document link when a prior link expires or you retrieve a document with list_documents. Requires an active RemplirPDF subscription.

Instructions

Renvoie un nouveau lien de téléchargement du PDF (valable 24 h) et le lien du document dans l'application, pour un document du compte. À utiliser quand un lien précédent a expiré ou pour un document retrouvé avec list_documents ; ne crée ni ne modifie aucun document (pour générer, utilisez generate_document). Nécessite un abonnement RemplirPDF actif.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`document_id`	Yes	Identifiant du document (doc_…), renvoyé par generate_document ou list_documents.

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Titre du document.
`app_url`	Yes	Page du document dans l'application RemplirPDF (connexion requise) : modifier, envoyer, faire signer.
`document_id`	Yes	Identifiant du document.
`download_url`	Yes	Lien de téléchargement direct du PDF, sans connexion, valable 24 h.
`download_expires_at`	Yes	Date d'expiration du lien de téléchargement (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 18, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: the 24-hour link validity and the requirement for an active RemplirPDF subscription, which is an entitlement gate the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the return value before the usage conditions, and each clause (validity, when-to-use, when-not, alternative, prerequisite) carries distinct information. It is dense and clause-heavy but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers usage, the non-mutating nature, and the subscription precondition. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, and schema coverage is 100% – the schema already documents document_id with its doc_ prefix and its provenance (generate_document/list_documents). The description adds nothing param-specific beyond 'pour un document du compte', so the baseline 3 is right.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns a new PDF download link (valid 24h) plus the in-app document link, scoped to a document of the account. It explicitly distinguishes itself from generate_document, so an agent can tell the two apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions ('quand un lien précédent a expiré', 'pour un document retrouvé avec list_documents') and a when-not clause ('ne crée ni ne modifie aucun document'), plus the named alternative generate_document for generation. Something close to a complete routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server