Skip to main content
Glama
GaijinEntertainment

Pararam Nexus MCP

delete_post

Delete a post you authored in a chat. Provide the chat ID and post number to remove it.

Instructions

Delete a post.

Args: chat_id: Numeric chat ID. post_no: Post number to delete (must be authored by the token's user).

Returns: ToolResponse confirming the delete and the resulting is_deleted flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYes
post_noYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
messageYesHuman-readable summary of the result
payloadNoThe actual response data
successYesWhether the operation was successful
Behavior3/5

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

No annotations provided, so description carries full burden. Describes destructive action and ownership constraint, and mentions return flag. However, lacks details on permanence, error conditions, or side effects.

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?

Extremely concise: one-line action, then short Args and Returns. No wasted words, front-loaded.

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?

Covers core aspects: action, required params, authorship constraint, return value. Could include error handling or permanence, but adequate for a delete tool with output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no descriptions (0% coverage). Description adds meaning: chat_id as numeric, post_no as post number with authorship constraint. This compensates for schema gaps, but chat_id explanation is minimal.

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 'Delete a post' with verb and resource. Distinguishes from sibling 'edit_post' and others. The additional ownership constraint further clarifies scope.

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?

Description implies usage (delete a post) but does not explicitly state when to use vs alternatives like 'edit_post' or when not to use. No exclusion criteria or alternative tool mentioned.

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/GaijinEntertainment/pararam-nexus-mcp'

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