Skip to main content
Glama

Check a listing

check_listing
Read-only

The status of a listing from submit_listing. Once it is live, also its badge and share links and the last 30 days of numbers: page views, clicks to the site, times AI agents got it, and sites showing its badge.

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

Input Schema

NameRequiredDescriptionDefault
listingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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. The description adds valuable behavioral context by explaining the conditional return data: once a listing is live, it also returns badge and share links plus specific 30-day metrics. It does not cover error behavior or auth needs, but for a read-only status check this is largely sufficient.

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?

The description is short and front-loads the core purpose (status of a listing) before listing additional return data. The second sentence is slightly run-on with repeated 'and', but no information is wasted.

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 simple read-only tool with one parameter and no output schema, the description covers the main return contents well, including conditional metrics. The only notable gap is that it does not document the listingId parameter explicitly, but overall an agent has enough to call it correctly.

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 description coverage is 0%, so the description must compensate for the single listingId parameter. It implies the ID comes from submit_listing, which adds helpful source context, but it never explicitly names the parameter or explains its expected format beyond that implication.

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 clearly identifies the resource (a listing from submit_listing) and what is retrieved (status, and once live, badge, share links, and 30-day metrics). It distinguishes itself from submit_listing by focusing on checking an existing listing rather than creating one.

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?

The phrase 'from submit_listing' implies this tool is used after submitting a listing to check its status, which provides useful context. However, it does not explicitly state when to use this versus other tools, nor does it mention any exclusions or prerequisites such as required permissions.

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