delete_docPermanently delete a page you own (requires an lp_ API key). The URL stops serving immediately and cannot be recovered.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The document slug — the path part of its https://lucid.page/<slug> URL. |
| Name | Required | Description | Default |
|---|---|---|---|
| deleted | Yes | Slug of the deleted page |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While destructiveHint=true already flags the destructive nature, the description adds valuable specifics: deletion is permanent, the URL stops serving immediately, and the document cannot be recovered. It also discloses the authentication requirement. No contradiction with annotations.
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?
Two short sentences convey the action, ownership requirement, auth requirement, immediacy, and irreversibility. Every clause earns its place, and the most important information is front-loaded.
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?
For a single-parameter destructive tool with full schema coverage and an output schema, the description covers everything an agent needs: what it does, who can use it, what happens, and the permanence. Nothing critical is missing.
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 already fully documents the slug parameter. The description adds no additional parameter-level semantics beyond the schema, which is the expected baseline.
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 uses a specific verb ('delete'), names the resource ('page/document'), and adds critical qualifiers ('permanently', 'you own'). It clearly distinguishes this from sibling tools like get_doc, update_doc, and publish_doc.
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 clearly states the precondition for use: the page must be owned and an lp_ API key is required. It does not explicitly enumerate alternatives or when not to use the tool, but the usage context is clear enough for an agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource-action pair: doc CRUD, bundle creation, listing, and account limits. get_doc vs list_docs clearly separates single-fetch from collection listing, and publish/update/delete/are unambiguous.
All tools follow a consistent snake_case verb_noun pattern: create_bundle, delete_doc, get_doc, get_limits, list_docs, publish_doc, update_doc. The verbs are clear and the nouns match the resource, though list_docs is a natural pluralization.
With 7 tools, the server is well-scoped for a document publishing platform. Each tool covers a distinct core operation without redundancy or bloat, fitting comfortably in the ideal 3-15 tool range.
The document lifecycle is complete (create, read, update, delete, list), but bundles only have a create operation with no get/update/delete. Also, publish_doc returns a claim_token for anonymous publishes, yet no claim tool is exposed, forcing users to an external endpoint.