Report Unsupported Request
report_unsupported_requestRecords that the customer asked for a change this connector has no tool for (for example editing contact-form fields, footer link columns, deleting a site, taking a site offline, restoring a backup). Stores only a short kebab-case capability name (e.g. form-fields) and an optional one-line note in general terms; the note is refused if it contains an email address, phone number or web address, and nothing else from the conversation is stored. Does not change the site. Returns a link to the Zarla editor, where the customer can make the change themselves.
Annotations: read-only=false, destructive=false, idempotent=false, open-world=false. Why: Records that a request could not be served so Zarla can add the capability; appends a note, overwrites nothing (additive, not destructive). Not idempotent: each call records another note. Closed-world.
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": {
"capability": "<capability>"
},
"name": "report_unsupported_request"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| detail | No | One line, general terms only — no names, contact details or web addresses | |
| site_id | No | The site it was about, if known | |
| capability | Yes | Kebab-case name of the missing capability (e.g. form-fields, footer-links, delete-site, unpublish-site, restore-backup, multi-page-build) — never the customer's content or words | |
| tool_tried | No | The tool that couldn't do it, if one was attempted (e.g. update_block) |