Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Set submission delivery

set_delivery
DestructiveIdempotent

Configure where a page's form submissions are delivered: type "email" (an address the user chose) or type "http" (any CRM API / Zapier / Make / n8n webhook / custom backend, with headers and a field mapping). Load get_skill_delivery_integrations BEFORE using this — it defines the required workflow: research the target API, build the mapping yourself, confirm details with the user, and NEVER ask for credentials in chat — create without secrets and send the user the returned settingsUrl to add auth securely.

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": {
      "pageId": "<pageId>",
      "type": "<type>"
    },
    "name": "set_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
httpNotype=http: endpoint config. { url (https), method? (POST|PUT|PATCH), headers? {name: value}, mapping? {formField|$form|$page|$submittedAt|$meta.<key>: "target.dot.path"}, where <key> is one of country, timezone, language, device, browser, os, utm_source, utm_medium, utm_campaign, utm_term, utm_content, pageVersion, marketingConsent; constants? {"target.dot.path": "literal value"} }. Without mapping, the default JSON shape {form, page, submittedAt, data, meta} is sent. Failed http deliveries fall back to email so submissions are not lost.Header values are write-only: responses mask them as ******** and sending the mask back keeps the stored value.
typeYesIntegration type.
emailNotype=email: destination address. Omit or pass empty to reset to the account email.
pageIdYesThe pageId returned when the page was published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations flag a destructive, open-world write, and the description goes well beyond them: it discloses the two-phase credential flow (create without secrets, hand back a settingsUrl), that header values are write-only and masked as ******** on read-back, and that failed http deliveries fall back to email so submissions are not lost. These are non-obvious behaviors an agent could not infer from the annotations or schema alone.

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 purpose and the two modes are front-loaded, and the prerequisite/credential warning follows immediately. The content is dense with useful detail, though the second sentence is a long chain of clauses joined by dashes and commas that could be split for faster scanning.

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 nested-object mutation with no output schema, the definition covers the required workflow, credential handling, the returned settingsUrl, and failure fallback. It does not say what happens to an existing delivery configuration when this is called (replacement vs merge) or whether page-ownership permission is required, which matters given destructiveHint=true.

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% and the http sub-object schema already documents url/method/headers/mapping/constants, the default JSON payload shape, and the empty-email reset behavior. The description's contribution is mainly reframing those fields ('an address the user chose', 'headers and a field mapping') rather than adding new constraints, so the baseline 3 applies.

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?

States a specific verb and resource - configuring where a page's form submissions are delivered - and enumerates the two supported modes (email address vs http endpoint to CRM/Zapier/Make/n8n/custom backend). This is clearly distinguishable from sibling skill/read tools like get_skill_delivery_integrations or set_form_rules.

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

Usage Guidelines5/5

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

Explicitly mandates loading get_skill_delivery_integrations BEFORE use and summarizes the required workflow: research the target API, build the mapping yourself, confirm with the user, and never request credentials in chat. This is a clear when-and-how directive with a named prerequisite tool, not an implied usage.

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

All Pageree 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