Skip to main content
Glama

Add a page

add_page

Adds a page to the site's draft with its sections. The page appears in the site menu. The path is the page's address inside the person's own WebDesk site (for example /services), not a web address or an API endpoint.

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": {
      "site_id": "<site_id>",
      "path": "<path>",
      "title": "<title>",
      "sections": "<sections>"
    },
    "name": "add_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPage path: "/" for home, or "/services", "/gallery". Lowercase letters, digits and hyphens.
titleYes
site_idYesThe site id from list_sites or create_site.
sectionsYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false. The description adds genuine context beyond that: the page is written to the draft (not published), it becomes part of the site menu, and the path is scoped to the owner's own site rather than an external address. It does not say whether a duplicate path is rejected or merged.

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?

Three tight sentences, purpose first, then the menu side effect, then the path disambiguation that prevents the most likely misuse. No filler; only a slight redundancy between 'draft' and the path note.

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

Completeness3/5

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

For a creation tool with a large nested sections union and no output schema, the description covers the entry point and path trap but leaves the sections payload, minimum section count, and what is returned (page id? preview link?) to inference. Adequate but with clear gaps for a tool of this complexity.

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 coverage is only 40%, so the description must carry weight. It does a good job on 'path' — clarifying that it is the page's address inside the owner's site, not a URL or API endpoint — but says nothing about 'title' limits, the optional 'description', or how 'sections' should be shaped or ordered.

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

Purpose4/5

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

States a concrete verb and resource ('Adds a page to the site's draft with its sections') and adds two consequences: the page shows in the site menu and lives in the owner's own site. That is enough to distinguish it from add_section and update_page, though it does not name those siblings explicitly.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no named alternatives. An agent cannot tell from the description when to add a page versus adding sections to an existing page via add_section, or whether the site must exist first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources