Delete Blog Post
neuron_delete_blog_postDelete a blog post by providing its UUID. Removes the post from the system.
Instructions
Delete a blog post
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Post UUID |
neuron_delete_blog_postDelete a blog post by providing its UUID. Removes the post from the system.
Delete a blog post
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Post UUID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must disclose behavioral traits. It merely states the action without any details about irreversibility, permissions needed, or cascading effects, which are critical for a delete operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one sentence), but conciseness comes at the cost of completeness. It is not verbose, but lacks necessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a deletion tool with no output schema and no annotations, the description should at least indicate that deletion is permanent or confirm the action. It does not provide sufficient context for an AI agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (one parameter 'id' with description 'Post UUID'). The description adds no extra meaning beyond the schema, but baseline is 3 due to high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description 'Delete a blog post' is essentially a tautology of the tool name 'neuron_delete_blog_post'. It restates the name without adding any distinctive context or differentiation from sibling delete tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool vs. alternatives (e.g., unpublish vs. delete, or when deletion is appropriate). Prerequisites, side effects, or irreversible nature are not mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server