Skip to main content
Glama

Create page draft

create_page_draft
Idempotent

Create a private page draft in MyReach. This saves a draft but does not publish it. Use a random UUIDv4 or 32–64 hex nonce as requestId; reuse it only for retries and keep it private. Before signup, supply the intended owner's email. New pages stay private for 24 hours until verified owner claim. For an existing page, connect its owner's account.

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": {
      "requestId": "<requestId>",
      "slug": "<slug>"
    },
    "name": "create_page_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
contentNo
requestIdYes
ownerEmailNo

Output Schema

NameRequiredDescriptionDefault
noteYes
slugYes
statusYes
draftIdYes
revisionYes
expiresAtYes
publicUrlYes
baseRevisionYes
draftCapabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / content / properties / design / properties / primary / pattern
      Previous value: -"^#[0-9a-f]{6}$"New value: +"^#[0-9a-fA-F]{6}$"
    • changedInput schema / properties / content / properties / design / properties / secondary / pattern
      Previous value: -"^#[0-9a-f]{6}$"New value: +"^#[0-9a-fA-F]{6}$"
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses important lifecycle behavior: the draft remains private for 24 hours until verified owner claim, it does not publish, requestId must be a random UUIDv4 or 32–64 hex nonce, and it should be reused only for retries and kept private. This adds substantial operational and privacy context not covered by the annotations.

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?

The description is appropriately short and front-loads the core action and privacy/non-publication behavior. The only slightly unclear sentence is 'For an existing page, connect its owner's account,' but overall it is efficient.

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?

The tool is complex, with nested content objects and an output schema, so the description does not need to explain return values. Still, it omits the meaning of slug and the top-level content object, and does not clarify the create-versus-update workflow, leaving gaps for an agent selecting and invoking this tool correctly.

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?

Top-level schema description coverage is reported as 0%, so the description carries extra burden. It explains requestId generation and retry semantics and when to supply ownerEmail, but it does not explain the meaning or constraints of slug or the top-level content object, leaving half of the required parameters without added semantic guidance.

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 clearly states the verb and resource: 'Create a private page draft in MyReach,' and clarifies that it saves but does not publish. It does not explicitly differentiate itself from the sibling update_page_draft, so it falls short of a 5.

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?

The description gives useful prerequisites and conditions, such as supplying the owner email before signup and connecting an existing owner's account. However, it does not explicitly say when to use this tool versus update_page_draft, get_page, or request_publication_approval, leaving the main alternative-routing question unresolved.

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