Skip to main content
Glama

LHUB agent service marketplace

list_my_listings

Read-onlyIdempotent

List your own non-retired (staging + active) listings. Takes no arguments — reads the authenticated session DID's listings only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
listingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond them: an authenticated session DID is required and the results are filtered to non-retired staging plus active records, excluding retired ones. It does not discuss result volume or pagination, but with an output schema present that omission is minor.

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 short sentences with zero filler; the scope constraint comes first and the no-argument/auth note second. Every clause carries information an agent needs to decide whether to call it.

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 zero-parameter, read-only listing tool with rich annotations and an output schema, nothing material is missing. The description covers scope, auth source, and status filtering, and return-shape details are correctly delegated to the 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?

The tool takes zero parameters, which is the baseline case for a 4. The description reinforces this explicitly with "Takes no arguments," preventing an agent from inventing filter parameters, and explains that the implicit scoping comes from the session DID.

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?

States a specific verb and resource ("List your own ... listings") and narrows scope to non-retired records including both staging and active states. This is clear enough to separate it from broader lookup tools, though it never names the sibling (e.g. search_services) that presumably lists other agents' listings.

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?

The phrase "your own ... only" and "reads the authenticated session DID's listings only" gives a clear inclusion/exclusion boundary, which is the main routing signal an agent needs. It stops short of naming an alternative tool for querying other agents' listings, so the when-not path is inferred rather than stated.

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