Thoth MCP Server

update-post

Update an existing post by modifying title, content, platform-specific variations, and status.

Instructions

Update an existing post. Can modify title, content, platform-specific variations, and status.

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": {
      "postId": "<postId>"
    },
    "name": "update-post"
  }
}

Input Schema

Name	Required	Description
`postId`	Yes	The UUID of the post to update
`title`	No	Updated title for the post
`originalContent`	No	Updated original content
`platformContents`	No	Updated platform-specific content variations
`status`	No	Updated post status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.4Jun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description must fully disclose behavior. Only states 'Update' without specifying merge vs replace, side effects, idempotency, or permissions. Major gaps for a mutation tool.

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?

One sentence, 12 words, front-loaded with purpose. Efficient, but could include more behavioral details without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

5 parameters, 1 required, 1 enum, 1 nested object, no output schema. Description lacks details on partial updates, return value, and behavior. Incomplete for the complexity.

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 coverage is 100%, so baseline is 3. Description adds marginal value by listing field categories, but schema already describes each parameter.

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?

Clearly states the verb 'Update' and the resource 'existing post'. Lists modifiable fields. Distinguishes from siblings: create-post, get-post, get-all-posts, etc.

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?

Implies usage for updating posts but gives no explicit when-to-use or when-not-to-use, nor alternatives. Only a single sentence without context.

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

Deploy Server