Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Edit blog design

blog_design_edit

Edit a blog design by applying changes to the templates. The blog title and description are blog settings returned by get_blog and changed by update_blog. A design never changes them.

'blog_design_template_format' documents the template format the changes must follow. Notices in the result report template problems for the user to review; a notice does not undo the checkpoint.

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": {
      "DesignID": "<DesignID>",
      "CheckpointID": "<CheckpointID>",
      "EditToken": "<EditToken>",
      "CheckpointTitle": "<CheckpointTitle>",
      "Changes": "<Changes>"
    },
    "name": "blog_design_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ChangesYesChanges for the new checkpoint, grouped by template or image; templates left out stay as they are.
DesignIDYesDesign UUID this checkpoint belongs to.
EditTokenYesEdit token from a full read of the checkpoint. Required before this edit.
CheckpointIDYesCheckpoint UUID to edit. Must belong to DesignID.
CheckpointTitleYesShort description of the change in this new checkpoint.

Output Schema

NameRequiredDescriptionDefault
NoticesYesProblems found in the templates, for the user to review. The checkpoint was still saved.
NewCheckpointYesNewly created checkpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Changes / description
      Added value: +"Changes for the new checkpoint, grouped by template or image; templates left out stay as they are."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations it discloses real behavior: notices report template problems without undoing the checkpoint, so a notice is non-fatal and partial success is possible — valuable for an agent deciding whether to retry. It also clarifies a scoping invariant (design edits never touch blog title/description). It does not say whether the edit goes live immediately or must be activated/saved, which is the bigger behavioral question given the activate/save siblings.

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?

Front-loaded with the core purpose in sentence one, followed by scoping, format reference, and result semantics in descending importance. Zero filler, though the settings paragraph is slightly tangential to the call itself.

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 five required params, nested per-template change objects, and an existing output schema, the description covers the essentials: what it mutates, the format contract, and how to interpret notices. Deeper checkpoint/activation lifecycle detail would help but is largely inferable from sibling names and the schema.

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%, including detailed OldString/NewString matching rules, so the schema does the heavy lifting and the baseline is 3. The description adds only the pointer to the template format documentation; it adds nothing about CheckpointTitle, EditToken acquisition, or the per-template Change grouping.

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?

States a specific verb and resource: 'Edit a blog design by applying changes to the templates.' It also draws a boundary against update_blog by explaining that blog title/description are settings, not design. It does not distinguish itself from blog_design_save or blog_design_activate, which the agent must infer.

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?

It gives useful routing guidance: blog title/description belong to get_blog/update_blog, and 'blog_design_template_format' documents the required template format. However, it never states when to call this versus blog_design_save, blog_design_create, or blog_design_checkpoint_restore, nor does it state prerequisites such as reading the checkpoint first (that lives only in the schema).

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

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