dForms

Duplicate a workspace link page

duplicate_link_page

Copy a page under a new slug, unpublished and never the default, so it can be edited (for the next event, say) before update_link_page publishes it. Any member can use it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>"
    },
    "name": "duplicate_link_page"
  }
}

Input Schema

Name	Required	Description
`name`	No	The copy's internal name. Absent: the original's.
`slug`	No	The copy's address after /p/. Absent: the original's with -2, -3 and so on.
`page_id`	Yes	The page id, from list_link_pages.
`workspace_id`	No	The workspace this call acts in: an id from list_my_workspaces. Required for a person signed in with several workspaces and for staff of this deployment; optional with an API key or with only one workspace.

Output Schema

Name	Required	Description
`live`	Yes	True when the page is saved with enabled: true, so public_url serves it. False: public_url answers 404.
`name`	Yes	The internal name; blank when nobody named it.
`page`	Yes	The stored page, ready to send back to update_link_page after changing it; null when there is none.
`slug`	Yes	The page slug; the default page is served at /{accountCode} whatever its slug.
`forms`	Yes	The workspace forms a form button can point at, by id.
`page_id`	Yes	The page id; null when the workspace has no page yet.
`brand_kit`	Yes	The brand kit the page takes its type, default colors and default logo from.
`workspace`	Yes	The workspace this call acted in, to compare with the one the user means.
`is_default`	Yes	True for the page at /{accountCode}.
`public_url`	Yes	The page address, to give to users exactly as returned; null when the deployment has no public address.
`account_code`	Yes	The workspace code the pages live under.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the duplicate is unpublished, is never the default, and can be edited before publication. It also clarifies the permission model by stating any member can use it, though it does not explicitly discuss repeated-call behavior or whether all page content is copied.

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 a single compact sentence with the core action and result front-loaded, and every clause adds useful context. There is no redundant or filler wording.

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?

The definition is complete for a duplicate operation: annotations cover safety, the schema fully documents parameters, and an output schema exists. The description supplies the key behavioral context about publication state, default status, editability, and permissions.

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?

Schema description coverage is 100%, so the schema already documents all four parameters, including defaults for name and slug. The description adds the general concept of a new slug but does not provide meaning beyond the schema for individual parameters.

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 states a specific verb and resource: 'Copy a page under a new slug.' It also distinguishes the result from normal publishing by saying the copy is unpublished and never default, so an agent can tell this apart from create_link_page or update_link_page.

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?

It explains the intended workflow clearly: duplicate first so the copy can be edited before update_link_page publishes it, and notes that any member can use it. It names update_link_page as the publishing alternative, but does not explicitly state when to use create_link_page instead of duplicating.

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

All dForms tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?