Skip to main content
Glama

Update live blog settings

update_blog_settings
Destructive

Change blog settings immediately on the live blog, only when requested by the user. Requires both edit and publish permissions. Read get_blog_settings first and supply its revision. Omitted fields are preserved; supplied menus replace that menu. Header/footer HTML is custom code. Images must come from upload_asset.

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": {
      "revision": "<revision>",
      "settings": "<settings>"
    },
    "name": "update_blog_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYesExact quoted revision returned by get_blog_settings.
settingsYes

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 declare the destructive/non-idempotent profile, and the description adds real context beyond them: required edit+publish permissions, optimistic concurrency via revision, and the crucial patch semantics ("Omitted fields are preserved; supplied menus replace that menu"). It also flags that header/footer HTML is executed custom code, which is a meaningful risk note.

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?

Five short sentences, front-loaded with the user-consent gate and the hard prerequisite. Every sentence carries distinct, non-redundant information; nothing could be cut without losing a constraint.

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 destructive nested-object mutation with no output schema, the description covers permissions, concurrency, partial-update behavior, and asset sourcing. Minor gaps remain: it does not state what happens on a revision mismatch or whether a new revision is returned.

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 only 50%, so the description usefully compensates: it explains where revision comes from, that menu arrays replace wholesale (empty array clears), and that image URLs must originate from upload_asset. It does not cover every nested field, but the highest-risk parameters are clarified.

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 and resource ("Change blog settings") plus scope ("immediately on the live blog"), which cleanly separates it from the read-only sibling get_blog_settings. An agent knows exactly what this tool mutates without opening the schema.

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?

Explicit gating ("only when requested by the user"), an explicit prerequisite workflow ("Read get_blog_settings first and supply its revision"), and an explicit dependency for images ("must come from upload_asset"). Alternatives and conditions are named rather than inferred.

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