Skip to main content
Glama

Save email footer

brand_set_footer
Idempotent

Saves the footer every email carries, above the mailing address and unsubscribe link (those two are always added and cannot be changed here): up to 5 full-width link buttons (links, for example Shop men’s, Find your store), the "Follow us" social icon row (social handles plus social_icons: true), and a small disclaimer (pricing or legal note). Fields you leave out stay as they are; links: [] removes the buttons, disclaimer: "" removes the note. Applies to every email sent after saving, including scheduled ones that have not gone out yet. Uses no quota and sends nothing. Read brand_get first and only save what the person approved. Example: {"links": [{"label": "Shop men’s", "url": "https://shop.example/men"}, {"label": "Find your store", "url": "https://shop.example/stores"}], "social": {"instagram": "shopexample", "youtube": "shopexample"}, "social_icons": true, "disclaimer": "Prices may differ in stores."} Requires API key scope: draft.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "brand_set_footer"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoFooter link buttons, top to bottom. Replaces the current list.
socialNoSocial profiles: a handle ("shopexample", "@shopexample") or the profile link. "" removes one. These are the same profiles as Settings > Brand.
disclaimerNoSmall print above the address, for example pricing, shipping or legal notes. **bold**, *italic* and [links](https://...) work. "" removes it.
social_iconsNotrue: show the profiles as a "Follow us" row of icons. false: plain text links (the older look).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only give the generic safety profile (not read-only, non-destructive, idempotent, closed-world); the description adds the details that actually matter: partial-update semantics ("Fields you leave out stay as they are"), explicit removal syntax (links: [] and disclaimer: ""), blast radius across scheduled campaigns, no quota consumption, and the required API key scope "draft". None of that is derivable from the 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?

It is front-loaded with the resource definition and scope exclusions before the update semantics and example, so an agent gets the essentials in the first sentence. It runs long, and the closing JSON example partly restates schema-documented structure, but every paragraph carries operational information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with nested objects, no output schema and no required fields, the description covers everything an agent needs: what is written, what is untouched, how to clear values, when the change takes effect, that nothing is sent, and the auth scope. Nothing consequential is left to inference.

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 baseline is 3; the description earns an extra point by documenting behavior the schema does not, notably the leave-out-means-unchanged rule and the max of 5 full-width buttons, plus a worked example tying label/url, social handles, social_icons and disclaimer together. The removal syntax (links: [], disclaimer: "") is largely duplicated from the schema, so it falls short of a 5.

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?

"Saves the footer every email carries" is a specific verb plus resource, and the description immediately bounds the scope by naming what is excluded ("above the mailing address and unsubscribe link (those two are always added and cannot be changed here)"). It also enumerates the exact contents of the resource (link buttons, social icon row, disclaimer), which separates it cleanly from siblings like brand_set_theme and brand_set_voice.

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?

It states an explicit prerequisite workflow: "Read brand_get first and only save what the person approved." It also tells the agent when the effect applies ("every email sent after saving, including scheduled ones that have not gone out yet") and clarifies that it does not send anything, which rules out misuse as a send operation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources