Skip to main content
Glama

Add Page

add_page

Add a new page to the site with default content blocks. Supported types: "service", "location", "about", "contact", "custom", "landing", "blog".

Annotations: read-only=false, destructive=false, idempotent=false, open-world=false. Why: Adds a new page to the DRAFT; nothing existing is overwritten (additive, not destructive). Not idempotent: each call adds another page, and may spend AI credits when it writes a service or location page. Closed-world: it talks only to Zarla's own services, including Zarla's AI generation. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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>",
      "page_type": "<page_type>",
      "title": "<title>"
    },
    "name": "add_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL slug. Auto-generated from title if omitted.
titleYesPage title (e.g. "Ceramic Coating", "Parramatta")
site_idYes
page_typeYes
descriptionNoBrief description to guide content generation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations are unusually rich, already disclosing that the page lands in the draft, that publish is separate, that calls are not idempotent, and that AI credits may be spent. The description adds only the 'default content blocks' behavior and the type list, which is useful but modest beyond what the structured data carries.

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?

Two short sentences, front-loaded with the core action, with the type list placed second. The enum enumeration is somewhat redundant with the schema but costs little and aids scanning.

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 no output schema, the description never indicates what is returned (such as the new page identifier) or that the created page starts as an editable draft. Some of that is covered by the annotations, but the definition itself leaves the post-call state underspecified.

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 60%, so title and description are already documented in the schema; the description only restates the page_type enum values without explaining how type affects generation (e.g., that service/location pages consume AI credits). No additional meaning is added for site_id or slug.

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?

The description gives a specific verb and resource ("Add a new page to the site") plus a distinguishing detail, "with default content blocks," and enumerates the supported page types. It is clear what the tool does, though it does not explicitly contrast with siblings like create_site or add_block.

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

Usage Guidelines3/5

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

Usage is only implied by naming the tool 'add page' and listing valid types; there is no statement of when to choose this over add_block or create_site, and no prerequisites such as needing an existing site_id are mentioned. An agent can infer the general case but gets no routing guidance.

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.