Help by DeltaBreen

save_ticket_pages

Idempotent

Save a site's ticket pages layout as a draft. Customers keep seeing what was published before until publish_ticket_pages.

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": {
      "product_id": "<product_id>",
      "html": "<html>"
    },
    "name": "save_ticket_pages"
  }
}

Input Schema

Name	Required	Description
`css`	No	The layout's CSS. It applies inside the layout only. No @import and no backslashes.
`html`	Yes	The layout's HTML: a data-help="list" part holding one data-help="row", and a data-help="ticket" part holding data-help="messages" (with one data-help="mine" and one data-help="theirs", each holding a data-help="text"), a <textarea data-help="reply"> and a <button data-help="send">. get_ticket_pages lists every part. Scripts, images, inline styles and handlers are removed.
`product_id`	Yes	The site's id (a uuid), from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- changedInput schema / properties / css / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true), so the description's job is to add context — and it does, disclosing the draft/published visibility split that is the key behavioral consequence of calling this tool. It omits any note on validation failures or content stripping behavior, which lives only in the schema.

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?

Two short sentences, front-loaded with the action and followed by the consequence. Every clause carries information; nothing is redundant with the title or annotations.

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?

For a three-parameter save-draft tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the lifecycle context an agent needs. The only gap is the relationship to validation siblings like check_ticket_pages, which the agent must infer.

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 100% and the html/css/product_id descriptions are detailed, so the description adds no parameter meaning beyond the schema. That is the expected baseline-3 case rather than a gap.

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 names a specific verb and resource ('Save a site's ticket pages layout as a draft') and explicitly contrasts it with publish_ticket_pages, so an agent can distinguish it from get_ticket_pages/check_ticket_pages without reading the schema.

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 states the operative context — draft saving, with live customers unaffected until publish_ticket_pages is called — which implicitly tells the agent when to use this versus the publish sibling. It stops short of naming explicit exclusions or prerequisites such as validating with check_ticket_pages first.

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

All Help by DeltaBreen 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?