Polyblog Multilingual Blog

Edit a blog post

update_article

Destructive

Use this when someone asks to change a blog post's title, text, summary, slug, author or categories, or to publish or unpublish it. Returns the updated post; only the fields passed change, and each edit notifies the blog's webhooks. Not for adding a translation.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Id of the post to change
`slug`	No	New URL slug, up to 300 characters; changes the post's URL
`title`	No	New title, up to 300 characters
`author`	No	New author name, up to 200 characters
`format`	No	markdown or html, describing how content is written
`content`	No	New body in the post's format, up to 100,000 characters; replaces the whole body
`published`	No	true publishes the post, false turns it back into a draft
`categories`	No	Complete new list of up to 50 categories; replaces the old list
`description`	No	New summary, up to 1,000 characters

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`article`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 28, 2026

addedInput schema / properties / author / description

Added value: +"New author name, up to 200 characters"

addedInput schema / properties / categories / description

Added value: +"Complete new list of up to 50 categories; replaces the old list"

addedInput schema / properties / content / description

Added value: +"New body in the post's format, up to 100,000 characters; replaces the whole body"

addedInput schema / properties / description / description
```
Added value: +"New summary, up to 1,000 characters"
```

addedInput schema / properties / format / description

Added value: +"markdown or html, describing how content is written"

changedInput schema / properties / id / description

Previous value: -"Article id to update"New value: +"Id of the post to change"

addedInput schema / properties / published / description

Added value: +"true publishes the post, false turns it back into a draft"

addedInput schema / properties / slug / description

Added value: +"New URL slug, up to 300 characters; changes the post's URL"

addedInput schema / properties / title / description
```
Added value: +"New title, up to 300 characters"
```

First observedSep 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes beyond the annotations by disclosing partial-update semantics ('only the fields passed change'), the return value, and the side effect that each edit notifies the blog's webhooks. The webhook disclosure meaningfully explains the openWorldHint=true and non-idempotent nature, and the partial-update note softens the destructiveHint=true by clarifying scope.

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?

Three tight sentences: invocation trigger, behavior/return, exclusion. Everything is front-loaded and every clause carries information an agent needs.

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?

With a rich schema and an output schema present, the description only needs to cover routing and mutation behavior, both of which it handles fully. Nothing required to call this tool correctly is missing.

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 every parameter is already documented in the schema. The description names the same editable fields but adds no syntax, format, or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 (change/edit) and resource (blog post) and enumerates the exact editable fields plus publish/unpublish. The closing exclusion ('Not for adding a translation') further separates it from list_article_translations and other siblings.

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?

Gives an explicit trigger ('Use this when someone asks to change...') and an explicit when-not ('Not for adding a translation'). The agent has a clear routing rule without needing to open any schema.

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

All Polyblog Multilingual Blog 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.

Resources

Need Help?