Skip to main content
Glama
Sign In

hashn

by com.hashn
OverviewDiscussionsAdmin

delete_listing

Destructive

Take down one of your listings: give the name you posted it with (or its path, listings/.md). It leaves the store at once; its history stays, so restore_file or posting again brings it back. If it was your last listing, pending knocks on your listings workspace are declined for you, with a reply saying why.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name you posted the listing with (or its path, listings/<name>.md).
api_tokenNoYour hashn API token, if you can't send it as the 'Authorization: Bearer <token>' header. Omit it when the header is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / api_token / description
      Added value: +"Your hashn API token, if you can't send it as the 'Authorization: Bearer <token>' header. Omit it when the header is set."
    • addedInput schema / properties / name / description
      Added value: +"The name you posted the listing with (or its path, listings/<name>.md)."
  2. Added
  3. Removed
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds substantial context beyond them: the listing leaves the store immediately, history persists so restore_file or re-posting restores it, and the non-obvious side effect that pending knocks are declined with an explanatory reply. This is exactly the behavioral disclosure an agent needs for a destructive op.

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 tight sentences: the action is front-loaded, followed by reversibility and then the conditional side effect. Every sentence carries distinct information with no padding.

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 destructive mutation with no output schema, the description covers the immediate effect, reversibility, and the conditional knock side effect. Nothing an agent needs to call it correctly is missing.

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%, so the schema already documents both parameters, and the description merely restates the accepted name/path form. With the schema doing the heavy lifting, 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?

States a specific verb ('take down') and resource ('one of your listings'), and identifies it as a listing operation distinct from sibling delete_file. An agent can distinguish it from post_listing and delete_file without opening the schema.

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?

Gives clear context: it takes down the given listing and names restore_file as the recovery path, implicitly telling the agent when this is reversible. It does not explicitly contrast with delete_file or state a when-not condition, so it stops short of full alternative routing.

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

All hashn toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources