GoodSender

Update Blog Settings

update_blog

DestructiveIdempotent

Create or patch publication settings for the API key's workspace. This is the only place the public title and description are set. SEO Title and SEO Description are publication-wide overrides for the blog homepage and archive, independent of the visible Title and Description. Omit either SEO field to preserve it, send text to replace it, or send "" to clear it and resume that field's current public-content fallback. Other empty string fields remain omitted. A title is required the first time settings are saved.

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": "update_blog"
  }
}

Input Schema

Name	Required	Description
`Theme`	No	Theme key: one of default, thisweekin, fieldnote.
`Title`	No	Reader-facing blog title shown on every blog page, in feeds and in subscription emails. Required on first create.
`SEOTitle`	No	Independent publication-wide search/social title override for the blog homepage and archive. Omit to preserve it, send text to replace it, or send an explicit empty string to clear it and resume the current public Title fallback. The server trims it and enforces the 255-character limit.
`SenderName`	No	Display name for newsletter From.
`Description`	No	Reader-facing one-line description shown on the blog and in its feed.
`SendingDomain`	No	Verified workspace domain for newsletter From.
`MailingAddress`	No	Physical mailing address for newsletter footer.
`SEODescription`	No	Independent publication-wide search/social description override for the blog homepage and archive. Omit to preserve it, send text to replace it, or send an explicit empty string to clear it and resume the current public Description fallback. Suggested snippet length is advisory.
`SenderLocalPart`	No	Mailbox local-part for newsletter From.

Output Schema

Name	Required	Description
`Theme`	Yes	Theme key. Says nothing about the Liquid design; see Design.
`Title`	Yes	Visible public blog title and the fallback search/social title when SEO Title is empty.
`Design`	Yes
`SEOTitle`	Yes	Stored publication-wide search/social title override for the blog homepage and archive, or empty when the current public Title supplies the fallback.
`SenderName`	Yes	Newsletter From display name if set.
`Description`	Yes	Visible public blog description and the fallback search/social description when SEO Description is empty.
`CustomDomain`	Yes	Custom blog hostname if set.
`SendingDomain`	Yes	Newsletter From domain if set.
`TitleIsCustom`	Yes	True when a real title is stored.
`WorkspaceName`	Yes	Workspace name placeholder.
`MailingAddress`	Yes	Footer mailing address if set.
`SEODescription`	Yes	Stored publication-wide search/social description override for the blog homepage and archive, or empty when the current public Description supplies the fallback.
`SenderLocalPart`	Yes	Newsletter mailbox local-part if set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare mutation, idempotency, open-world behavior, and destructive potential. The description adds meaningful field-level behavior: omission preserves SEO fields, empty strings clear them and resume fallbacks, other empty strings remain omitted, and a title is required on first save.

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 description is front-loaded with purpose, then moves directly into SEO-field behavior and first-save requirements. It is somewhat dense, and some details overlap with schema descriptions, but every sentence carries useful behavioral guidance.

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?

Given 9 parameters, full schema coverage, an output schema, and annotations, the description provides the missing behavioral context needed to call the tool correctly. It covers creation versus patching, SEO override semantics, empty-string handling, and the first-save title requirement.

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 description coverage is 100%, so the baseline is 3. The description adds cross-parameter semantics not fully captured by individual schema fields, especially the special empty-string clearing behavior for SEO fields and the first-save title requirement.

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?

State a specific verb-and-resource pair: 'Create or patch publication settings for the API key's workspace.' It also distinguishes itself from post-editing siblings by saying it is 'the only place the public title and description are set,' though it does not name the sibling tools directly.

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 when to use it by saying it creates or patches blog publication settings and is the only place title/description are set. However, it does not explicitly compare against alternatives like get_blog or edit_post, nor does it state when not to use it.

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

All GoodSender 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.