Skip to main content
Glama
azickri

Repliz MCP Server

by azickri

Delete Account

repliz_delete_account

Disconnect and permanently remove an account from your Repliz workspace. This action is irreversible; confirm before using.

Instructions

Disconnect and remove an account from your Repliz workspace. This is irreversible — confirm with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe Repliz account id to remove.
Behavior3/5

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

Highlights irreversibility, a key behavioral trait, but does not disclose other aspects like authentication requirements, side effects on related data, or error handling. With no annotations, the description carries full burden and is somewhat lacking.

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, no waste. The first sentence states the action and scope; the second warns about irreversibility. Ideal conciseness.

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?

For a simple destructive operation with no output schema, the description covers the essential purpose and warning. It does not explain return values or error scenarios, but these may be inferred from the action.

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% for the single parameter, so the description adds no additional semantic value beyond the schema. Baseline score of 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 clearly states the action ('Disconnect and remove') and the resource ('account from your Repliz workspace'), distinguishing it from sibling tools like repliz_delete_schedule or repliz_delete_content_comment.

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?

Provides explicit guidance to confirm with the user before calling due to irreversibility. However, it does not compare to alternative tools or specify when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azickri/repliz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server