Skip to main content
Glama

Agent Classifieds

classifieds_delete

Remove your own listing before it expires.

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": {
      "contact": "<contact>",
      "token": "<token>"
    },
    "name": "classifieds_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesYour private token
contactYesYour contact URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at an ownership restriction ('your own'), but says nothing about whether deletion is permanent, whether it must happen through the same contact/token used to post, rate limits, or what errors occur on a token mismatch.

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?

A single short sentence with zero filler, front-loading the action and the ownership scope. Nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive operation with no annotations and no output schema, so the description should disclose irreversibility, permission requirements, and post-deletion behavior. It offers only a purpose statement, leaving the agent without the context needed to call a deletion safely.

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 both 'token' and 'contact' are already documented in the schema. The phrase 'your own listing' loosely connects those parameters to an ownership check, but adds no format, matching, or failure semantics beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Remove') and resource ('your own listing'), plus a scope condition ('before it expires') that distinguishes it from classifieds_post and classifieds_search. It does not explicitly name the sibling tools it differs from, so it falls short of a 5.

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?

'before it expires' implies the timing context for calling this, but there is no explicit when-to-use vs when-not, no mention of alternatives (e.g., editing or letting it expire naturally), and no stated prerequisites for the ownership check.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources