dForms

List the workspace link pages

list_link_pages

Read-onlyIdempotent

Every public page of the workspace, the default (at /{accountCode}) first: its page_id, slug, internal name, whether it is live, how many buttons it holds and its public_url. Read it to find the page_id the other link page tools take. Any member can use it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_link_pages"
  }
}

Input Schema

Name	Required	Description	Default
`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
`max`	Yes	How many pages a workspace may keep.
`pages`	Yes
`workspace`	Yes	The workspace this call acted in, to compare with the one the user means.
`account_code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

While annotations cover safety (readOnlyHint:true), the description adds valuable behavioral details regarding the default scoping (pages at /{accountCode} are listed first) and permissions (Any member can use it).

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 efficient and front-loaded, listing the key output fields immediately after defining the resource. No sentences are wasted.

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

Completeness4/5

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

Given the low parameter complexity and strong annotations, the description provides all necessary context regarding what is returned, what the tool does, and its prioritization rules.

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?

With 100% schema coverage, the description doesn't need to explain parameters. The reference to the default behavior (i.e., when workspace_id is omitted) is valuable semantic context but aligns closely with the schema’s optional nature.

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 identifies the resource (public pages of the workspace) and explicitly lists the specific attributes returned, such as page_id, slug, and public_url.

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 clearly explains the tool's intended use case: to find page_id values required by other link page tools, which provides strong functional guidance.

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?