Skip to main content
Glama

get_listing_schema

Read-only

Every listing field with type, limits, allowed values (categories, industries) and guidance, plus licence types and white-label levels.

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": "get_listing_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's job is to say what comes back. It does enumerate the returned content categories, which is genuinely useful given there is no output schema. It does not say whether the result is a static catalog, how it is structured, or how large it is, so the added context is moderate rather than rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler, and the most important content (fields, types, allowed values) is front-loaded. It is a noun phrase rather than a verb-led statement, which makes it slightly less immediately scannable, but nothing is wasted.

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

Completeness3/5

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

With no parameters, no output schema and only a read-only annotation, the description must carry the return-value burden, and it only partly does: it lists content categories but not the response shape. For a trivial no-arg lookup this is close to adequate, though a note tying it to create_listing would make it complete.

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, so there is no parameter semantics to explain and the description cannot be faulted for omitting them. Baseline 4 applies for a no-argument tool whose description correctly implies no input is needed.

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 names a specific resource (listing schema) and enumerates the contents returned: field types, limits, allowed values such as categories and industries, licence types and white-label levels. An agent knows this is a metadata/catalog lookup rather than a data fetch. It stops short of 5 because the verb is only implied ('Every listing field...') and it never distinguishes itself from the sibling get_buyer_request_schema, which has an identical shape.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this, e.g. 'call before create_listing to discover valid fields and allowed enum values'. The closest sibling, get_buyer_request_schema, is not referenced as an alternative for a different resource, so the agent must infer the choice from names alone. Usage is only weakly implied by the word 'schema'.

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