Skip to main content
Glama
Sign In

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

Preview site email

preview_site_email
Read-onlyIdempotent

Render the saved email with sample data: subject, errors (errors send the default), warnings, plain text.

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": {
      "kind": "<kind>"
    },
    "name": "preview_site_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSite id.
kindYesSee list_site_emails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Email kind from list_site_emails."New value: +"See list_site_emails."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "order_receipt",
-  "subscription_welcome",
-  "order_shipped",
-  "gift_card_gifted",
-  "gift_card_self",
-  "customer_login",
-  "download_delivery",
-  "download_update"
-]New value: +[
+  "order_receipt",
+  "subscription_welcome",
+  "order_shipped",
+  "booking_confirmed",
+  "booking_requested",
+  "booking_declined",
+  "booking_balance",
+  "booking_deposit",
+  "booking_deposit_link",
+  "booking_agreement",
+  "booking_agreement_sign",
+  "booking_abandoned",
+  "gift_card_gifted",
+  "gift_card_self",
+  "customer_login",
+  "download_delivery",
+  "download_update"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "order_receipt",
-  "subscription_welcome",
-  "gift_card_gifted",
-  "gift_card_self",
-  "customer_login",
-  "download_delivery",
-  "download_update"
-]New value: +[
+  "order_receipt",
+  "subscription_welcome",
+  "order_shipped",
+  "gift_card_gifted",
+  "gift_card_self",
+  "customer_login",
+  "download_delivery",
+  "download_update"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Site id. Pass it on every call."New value: +"Site id."
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: rendering uses sample data, and the output carries an errors field whose presence means the live send falls back to the default email — context an agent could not infer from 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?

One front-loaded sentence with an explicit output-field list. The parenthetical 'errors (errors send the default)' is slightly cryptic and repetitive but carries real information, so nothing worth removing.

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?

No output schema exists, yet the description compensates by naming the four returned fields, and the input schema is fully self-describing. An agent has enough to call it correctly; only the exact error-case semantics remain a little terse.

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 100%, with id and the 17-value kind enum both documented (kind defers to list_site_emails). The description adds nothing about either parameter, so the baseline 3 applies.

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 specific verb+resource combination: 'Render the saved email with sample data', and enumerates the produced fields (subject, errors, warnings, plain text). This clearly distinguishes it from the adjacent get_site_email/update_site_email siblings, though it never names them explicitly.

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?

No explicit statement of when to call this versus get_site_email or update_site_email, nor any prerequisites. Usage is only implied by the phrase 'with sample data', which suggests checking a template before relying on it.

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

All PageHub toolsInspect
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