Foliyo

Save a project, and open its hub

save_project

DestructiveIdempotent

Save or update a client or project record with default sender, design guide, audience, presentation format and access settings. Optionally create a hosted project hub that groups its published pages. Existing pages retain their own access settings. Returns the saved project and any generated hub links and access code.

Input Schema

TableJSON Schema

Name	Required	Description
`hub`	No	true to give the project a hub, or your own address for it.
`gate`	No	How the hub is locked: "email" (each reader types an address once, and the report names them - prefer this) or "pin" (six digits everyone shares, so every reader stays anonymous). Also accepted: "password" (the old name for "pin"), "domain:acme.com", "none".
`name`	Yes	Short handle, e.g. "acme". Reusing one updates it in place.
`guide`	No	Saved design guide name to write this project's HTML to.
`label`	No	Shown on the hub, e.g. "Acme Q3".
`format`	No	Default presentation format for new pages.
`verify`	No	Email a code to prove the reader owns the address.
`audience`	No	Saved audience id: who reads this project by default.
`password`	No	The hub PIN, when gate is "pin". Six digits are minted if you omit it.
`senderId`	No	Saved sender identity, by id or label.
`shareGate`	No	Default gate for NEW pages: pin, email, domain:acme.com or none. Separate from the hub gate. Email/domain require Pro.
`description`	No	One line under the hub title.
`shareVerify`	No	Prove mailbox access for the default email/domain share gate.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / format

Added value: +{
+  "description": "Default presentation format for new pages.",
+  "enum": [
+    "web",
+    "slides-16-9",
+    "slides-flexible",
+    "interactive-static"
+  ],
+  "type": "string"
+}

First observedSep 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations disclose write, non-idempotent... actually idempotentHint=true, destructiveHint=true, openWorldHint=true. The description adds that reusing a name updates in place, that existing pages keep settings, and that the hub links and access code are returned – useful context beyond the hints. It does not spell out what 'destructive' means here or what gets overwritten on update, so it stops short of a 5.

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?

Three tight sentences: what it saves, the optional hub side effect, and the return value. Front-loaded with the verb and no wasted clauses.

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 13-parameter mutation tool with annotations present and no output schema, the description covers the main behaviors, the hub side effect, and the return value. It falls short only on update semantics (what happens to fields not passed) and permission requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 13 parameters. The description adds little parameter-level detail beyond what the schema carries, but it does frame the purpose of the hub/gate fields as a group. Baseline is 3; slight credit for grouping the concepts.

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 (save/update) and resource (client or project record) and enumerates the fields it manages. Sibling tools save_audience, save_guide, save_sender exist, so the 'client or project record' scope plus the hub-creation side effect clearly differentiates it.

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 implies this is the tool to persist a project and optionally its hub, and notes that existing pages retain their own access settings, but never states when to use it versus get_project or delete_project, nor prerequisites for hub creation.

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

All Foliyo 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?