Skip to main content
Glama

EX & GO marketplace

Get a listing

get_listing
Read-only

Get one listing by id or slug. Everyone sees public listings; a signed-in owner also sees their own listing while it waits for moderation — which is how you check whether a create actually succeeded.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=true and openWorldHint=false. The description adds real behavioral context beyond them: visibility depends on auth state, and an owner's unmoderated listing is only visible to that owner. It does not cover failure behavior for a nonexistent id, so it is not exhaustive.

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 sentences, front-loaded with the core action, then the visibility rule and the motivating use case. No filler, no restatement of the title or annotations.

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?

For a one-parameter read tool with no output schema, the description covers the two things that matter: what identifies the record and what the caller is allowed to see. It leaves the shape of a listing and not-found behavior unstated, which is a modest gap rather than a blocking one.

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 coverage is 0% — the single 'id' parameter has no description at all. The description compensates by revealing that the value may be either an id or a slug, which the schema does not convey; only the length/format constraints remain undocumented.

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 and resource with its lookup key ('Get one listing by id or slug'), and the singular 'one listing' plus the id-based lookup implicitly separates it from search_listings and list_* siblings. An agent knows immediately this is a single-record fetch, not a query.

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 an explicit use case — 'which is how you check whether a create actually succeeded' — telling the agent to call this after a create to verify persistence. It stops short of naming when NOT to use it (e.g., listing many results) or naming the search sibling, which keeps it out of 5 territory.

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