Repovive MCP Server

Block a user

repovive_block_user

Idempotent

Block a user to prevent direct messages to your account, optionally recording a reason. Reversible with the unblock tool.

Instructions

Block a user so they can no longer direct-message the authenticated account, with an optional reason. Reversible with repovive_unblock_user.

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": {
      "user_id": "<user_id>"
    },
    "name": "repovive_block_user"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No	Optional reason recorded with the block
`user_id`	Yes	User id to block

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already show this is a mutating, reversible, non-destructive operation. The description adds useful behavioral context by specifying the scope ('the authenticated account'), the recorded optional reason, and the fact that blocking is reversible with repovive_unblock_user. This goes beyond what the annotations provide without contradicting them.

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?

Two sentences carry the essential information with no filler: the effect, the optional reason, and the reversal path. The most important scoping detail ('can no longer direct-message the authenticated account') appears immediately, making the description easy to scan.

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 simple two-parameter tool with a complete input schema, an output schema, and relevant annotations, the description is fully sufficient. It explains what the action does, who it affects, and how to undo it, so an agent has everything needed to select and invoke the tool correctly.

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%, and the schema already documents both user_id and reason clearly. The description restates the optional-reason idea but adds no new parameter-level meaning beyond what the schema provides, so baseline 3 is appropriate.

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 action ('Block a user'), the exact target resource, and the precise effect: the blocked user can no longer direct-message the authenticated account. It also mentions the optional reason and explicitly names the reversal tool, distinguishing it from repovive_unblock_user and repovive_list_blocked_users.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description clearly indicates when to use this tool: when the goal is to stop a user from sending direct messages to the authenticated account. It also names the relevant alternative for undoing the action (repovive_unblock_user), though it does not explicitly list when-not-to-use conditions.

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

Deploy Server