doc.page PDF Extraction

create_doc_link

Publish a PDF as a tracked doc.page Doc Link and get back a shareable URL. The link belongs to the API key's account and also appears in its doc.page library. Requires an API key. Free plan: up to 3 active links; custom vanity slugs are premium-only. Optional expiry and open-notification toggle.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	http(s) URL of the PDF to publish (max 25 MB).
`name`	No	Display name in the library. Defaults to the filename.
`slug`	No	Custom vanity slug (premium plans only). Lowercase letters, digits and hyphens.
`expiresAt`	No	ISO 8601 date-time after which the link stops working. Omit for no expiry.
`notifyOnOpen`	No	Email the account owner on the first open. Default true.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses behavioral traits: link ownership (API key's account), library appearance, plan limits, and optional expiry/notifications. This is transparent but could mention rate limits or idempotency.

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

Conciseness5/5

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

The description is concise (two clear sentences plus clauses), front-loaded with the main purpose, and every sentence adds necessary information without redundancy.

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?

Given no output schema, the description adequately explains return value (shareable URL), creation behavior, plan context, and optional parameters. It covers all key aspects for an agent to decide and invoke correctly.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. The description adds context beyond schema by mentioning the premium restriction for slug and default behavior for name and notifyOnOpen. This adds moderate value.

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?

The description clearly states the action ('Publish a PDF as a tracked doc.page Doc Link') and the return value ('get back a shareable URL'). It distinguishes this tool from siblings like revoke_doc_link and list_doc_links.

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

Usage Guidelines4/5

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

The description mentions account requirements (API key), plan limitations (Free plan: 3 active links, premium vanity slugs), but does not explicitly state when not to use this tool or compare it to alternatives like get_doc_link_stats or list_doc_links.

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

All doc.page PDF Extraction tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct operation: PDF extraction, table extraction, chunking, link creation, listing, stats, and revocation. No overlapping purposes.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with lowercase and underscores, e.g., create_doc_link, extract_pdf, list_tables.

Tool Count5/5

Seven tools is an appropriate scope for a PDF extraction and link management server, covering both processing and lifecycle operations without excess.

Completeness4/5

Covers core extraction (text, tables, chunks) and link management (create, list, stats, revoke). Minor gap: no update operation for doc links, but not critical.

Resources

Need Help?