Skip to main content
Glama

List store listings

list_listings
Read-onlyIdempotent

Read OneStore listing drafts by locale: the canonical value shared by both stores, each store’s overrides (sent instead of the canonical value on push), and with includeLive the last values pulled from each store. Drafts are not a guarantee of the live store text. Paginated by locale.

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": {
      "appId": "<appId>"
    },
    "name": "list_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
cursorNo
localeNo
includeLiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeLive
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), and the description adds real behavioral context beyond them: the canonical/override/live data model, the warning that drafts are not a guarantee of live store text, and locale-based pagination. It stops short of describing page-size limits or cursor behavior, but the added semantics are substantive.

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?

Three sentences, front-loaded with the core purpose and then the data-model caveat; nothing is redundant. The phrasing is dense with domain jargon ('canonical value', 'overrides') in a single sentence, which costs a little readability but not correctness.

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?

With no output schema, the description does the work of explaining the returned shape (canonical value, store overrides, live values) and warns about draft/live divergence, which is the key correctness caveat. Remaining gaps are the paging mechanics and appId, which are minor for a read-only list tool.

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 carry parameter meaning. It explains includeLive and implicitly scopes locale and pagination, but says nothing about appId (the sole required parameter) or the cursor's role in paging, leaving two of four parameters undocumented anywhere.

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 opens with a specific verb+resource ('Read OneStore listing drafts by locale') and enumerates what is returned: canonical values, per-store overrides, and live values with includeLive. It is slightly muddled by the 'OneStore' vs 'both stores' framing, but an agent can still tell exactly what this tool returns and at what granularity.

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?

Usage is only implied: the includeLive flag is described ('with includeLive the last values pulled from each store'), which tells the agent when to set it. However, there is no explicit statement of when to call this tool versus another, nor any prerequisite or exclusion guidance, so the agent must infer the call context.

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