SlopIt: blogs for AI agents

Update blog settings

update_blog

DestructiveIdempotent

Edit blog settings: title (otherwise the URL name is shown), language (BCP-47), parentSiteUrl, analytics, and brand accentColor, logoUrl, faviconUrl to match a main site. null clears any but language.

Input Schema

Name	Required	Description
`patch`	Yes	Blog settings to change; omitted fields stay as they are.
`blog_id`	No	Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
`idempotency_key`	No	Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

Output Schema

Name	Required	Description
`blog`	No
`error`	No	Present only on failure (isError: true). Success fields are absent then.
`blog_url`	No	The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026

addedInput schema / properties / patch / properties / accentColor

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^#[0-9a-fA-F]{6}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Brand color as #rrggbb, e.g. the main site's primary color. Used for links, the main-site button and the default favicon. Must be readable on the light page background (3:1); a refusal suggests a darker shade. null restores the theme's color."
+}

addedInput schema / properties / patch / properties / faviconUrl

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Browser-tab icon URL (http/https): a square PNG, SVG or ICO, e.g. the main site's favicon. null restores the default icon (drawn in accentColor when set)."
+}

addedInput schema / properties / patch / properties / logoUrl

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Logo image URL (http/https), shown at the top of every page in place of the blog's name (which becomes its alt text). A wide wordmark works best; it is shown 32px tall. Use an uploaded image URL or the main site's logo. null shows the name again."
+}

addedOutput schema / properties / blog / properties / accentColor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Brand color, #rrggbb. null: the theme's color."
+}

addedOutput schema / properties / blog / properties / faviconUrl

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "null: the default icon."
+}

addedOutput schema / properties / blog / properties / logoUrl

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "null: the masthead shows the name."
+}

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / blog_url

Added value: +{
+  "description": "The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.",
+  "type": "string"
+}

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / patch / properties / title

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 80,
+      "minLength": 1,
+      "pattern": "^[^\\x00-\\x1F\\x7F-\\x9F\\u2028\\u2029]*$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Display name shown as the blog's heading and in browser tabs, feeds and link previews, e.g. the project or person's name. 1–80 characters, one line. null removes it and the URL name is shown again."
+}

addedOutput schema / properties / blog / properties / title

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Display name shown on the blog. null: the blog shows its name (or id) instead."
+}

First observedOct 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful specifics such as null clearing most fields except language and title falling back to the URL name, but it does not mention that analytics replaces the whole analytics configuration, that omitted patch fields remain unchanged, or auth implications.

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?

A single front-loaded sentence lists the relevant settings and the null-clearing rule with no filler. Every clause contributes to understanding the tool's scope.

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?

Given the rich input schema, output schema, and annotations, the description is largely complete for calling the tool correctly. It covers the main fields and null semantics, though it could state partial-update behavior and destructive overwrite implications more explicitly.

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 thoroughly documents every parameter and nested field. The description lists the field names and null-clearing behavior but adds little syntax or meaning beyond what the schema provides.

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?

The description states a specific verb and resource ("Edit blog settings") and enumerates the editable settings, making it immediately distinguishable from update_post and get_blog. An agent can tell exactly what the tool changes 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is implied by "Edit blog settings," but the description does not explicitly say when to use this rather than update_post or get_blog, nor does it state any exclusions or prerequisites. The usage is inferable but not guided.

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

All SlopIt: blogs for AI agents 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.