Foliyo

Save an identity to publish from

save_sender

DestructiveIdempotent

Save or update a sender identity used as the letterhead on published pages. Stores the supplied name, label, logo, accent and footer preferences. Setting makeDefault changes the default sender for future publishing. Sender logos and removal of Foliyo branding require Pro.

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": {
      "id": "<id>"
    },
    "name": "save_sender"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Short stable handle, e.g. "ashford". Reusing one updates it in place.
`name`	No	Name shown on the page. Defaults to the label.
`label`	No	What to call it when picking, e.g. "Ashford Advertising".
`accent`	No	Hex accent colour, e.g. "#1f3a8a".
`footer`	No	How much Foliyo shows at the bottom. White-label ('none') is a paid plan.
`logoUrl`	No	URL of a logo image. On Pro it leads the band at the top of the page. On the free plan the band keeps the Foliyo mark there and shows the name beside it; the logo is what upgrading buys.
`makeDefault`	No	Use this identity when the user names none.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedSep 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare a non-read-only, destructive, idempotent operation, and the description adds useful context that logo and branding-removal features require Pro. It also explains the makeDefault effect. It does not, however, clarify what a destructive update overwrites, whether omitted fields are preserved, or what permissions are needed.

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?

The description is front-loaded with the main action and is compact at four sentences. Each sentence adds relevant scope, default-behavior, or plan-gating information without waste.

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 seven-parameter mutation tool with full schema coverage and meaningful annotations, the description covers purpose, default behavior, and plan restrictions. The main omission is update semantics: it does not say whether omitted fields are preserved or whether saving with an existing id overwrites all sender settings.

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%, so the schema already carries most parameter meaning. The description restates the stored fields and adds plan-gating context for logos and branding removal, but it does not materially improve on the schema's parameter documentation.

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?

The description states a specific verb and resource: saving or updating a sender identity used as letterhead on published pages. It is clear what the tool does, but it does not explicitly distinguish itself from nearby tools such as save_project, save_guide, or get_sender/list_senders.

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?

Usage is implied by the publishing-letterhead context and the note that makeDefault affects future publishing. However, there is no explicit when-to-use guidance, no alternatives named, and no explanation of when to use get_sender or list_senders instead.

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?