MisarBlog MCP Server

Remove repost

remove_repost

DestructiveIdempotent

Undo a repost of a specific article by article ID and return the updated repost status and count. Use it to reverse an accidental or unwanted repost.

Instructions

Undo your repost of an article. Returns {reposted: false, repost_count}. Requires an API key; counts against your plan's request quota.

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": {
      "article_id": "<article_id>"
    },
    "name": "remove_repost"
  }
}

Input Schema

Name	Required	Description	Default
`article_id`	Yes	UUID of the article

Schema Changelog

Changes observed during successful MCP inspections.

Addedv5.2.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new operational context: the exact return payload {reposted: false, repost_count}, an API-key requirement, and that the call consumes plan quota. It does not say whether removing a repost is reversible or how errors surface, keeping it just below the top mark.

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 short sentences, each carrying distinct load: the action first, then the return shape, then the auth/quota constraints. Nothing is repeated from the annotation block and nothing is dead weight.

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?

For a one-parameter mutation with no output schema, the description supplies exactly what is missing elsewhere: the return payload, the credential requirement, and the quota cost. An agent has everything needed to decide to call it and to interpret the result.

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?

There is a single parameter, article_id, and schema description coverage is 100% with the UUID format and pattern fully specified. The description adds no meaning beyond the schema (e.g., whether the ID must reference an article you actually reposted), so the baseline of 3 applies.

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?

"Undo your repost of an article" gives a specific verb (undo/remove) and resource (repost), which cleanly separates it from the sibling repost_article. It stops short of naming that counterpart explicitly, so the pairing must be inferred rather than read.

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 phrase "undo your repost" implies the precondition (you must have already reposted this article), which is adequate implicit guidance. There is no explicit statement of when not to use it, what happens if no repost exists, or a pointer to repost_article as the inverse operation.

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