Skip to main content
Glama

listings_search

Read-only

Use this when you need an app's ref from its name, its publisher, a brand it works with or what it does ("create jira ticket"); one row per app, best match first. Do not use for popularity or rankings; use charts_get.

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": {
      "query": "<query>"
    },
    "name": "listings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryYesWords in app names, descriptions or publishers.
storeNo
cursorNo
contextNoThe user's goal, briefly.
publisherNoPublisher name, in any form.
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "app",
      -  "connector",
      -  "plugin",
      -  "desktop_extension",
      -  "directory_plugin",
      -  "directory_mcp",
      -  "bot",
      -  "skill",
      -  "unlisted"
      -]New value: +[
      +  "app",
      +  "connector",
      +  "plugin",
      +  "desktop_extension",
      +  "directory_plugin",
      +  "directory_mcp",
      +  "bot",
      +  "unlisted_plugin",
      +  "skill",
      +  "unlisted"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "app",
      -  "connector",
      -  "plugin",
      -  "desktop_extension",
      -  "directory_plugin",
      -  "directory_mcp",
      -  "bot",
      -  "unlisted"
      -]New value: +[
      +  "app",
      +  "connector",
      +  "plugin",
      +  "desktop_extension",
      +  "directory_plugin",
      +  "directory_mcp",
      +  "bot",
      +  "skill",
      +  "unlisted"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "app",
      -  "connector",
      -  "plugin",
      -  "desktop_extension",
      -  "directory_plugin",
      -  "directory_mcp",
      -  "bot"
      -]New value: +[
      +  "app",
      +  "connector",
      +  "plugin",
      +  "desktop_extension",
      +  "directory_plugin",
      +  "directory_mcp",
      +  "bot",
      +  "unlisted"
      +]
    • changedInput schema / properties / store / enum
      Previous value: -[
      -  "chatgpt",
      -  "claude",
      -  "cursor",
      -  "grokbot",
      -  "perplexity"
      -]New value: +[
      +  "chatgpt",
      +  "claude",
      +  "cursor",
      +  "grokbot",
      +  "perplexity",
      +  "muse"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "app",
      -  "connector",
      -  "plugin",
      -  "desktop_extension",
      -  "directory_rule",
      -  "directory_mcp",
      -  "bot"
      -]New value: +[
      +  "app",
      +  "connector",
      +  "plugin",
      +  "desktop_extension",
      +  "directory_plugin",
      +  "directory_mcp",
      +  "bot"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "app",
      -  "connector",
      -  "plugin",
      -  "desktop_extension",
      -  "directory_rule",
      -  "directory_mcp"
      -]New value: +[
      +  "app",
      +  "connector",
      +  "plugin",
      +  "desktop_extension",
      +  "directory_rule",
      +  "directory_mcp",
      +  "bot"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / store / enum
      Previous value: -[
      -  "chatgpt",
      -  "claude",
      -  "cursor",
      -  "grokbot"
      -]New value: +[
      +  "chatgpt",
      +  "claude",
      +  "cursor",
      +  "grokbot",
      +  "perplexity"
      +]
  7. First observed

TDQS

A4.1/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 then adds real behavioral context beyond them: results are one row per app, ordered by match quality, and the return payload is an app 'ref'. It does not address pagination, how limit/cursor interact, or how the kind/store filters change the result set, which keeps it short of a 5.

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, zero filler. The positive trigger and the query-intent examples come first, and the exclusion with its alternative comes second, which is the right ordering for an agent deciding whether to call this tool.

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 8 parameters, three enums, no output schema, and 38% schema coverage, the description covers intent, result cardinality and ordering but leaves the filtering and paging surface unexplained. An agent could call it correctly with just `query`, but would be guessing about `kind`, `store`, `cursor`/`limit` and what `response_format` changes. Adequate for the primary path, incomplete for the full surface.

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 only 38% across 8 parameters, so the description has to compensate. It does explain the searchable fields behind `query` and effectively covers `publisher` ('its publisher'), but `kind`, `store`, `limit`, `cursor`, `context`, and `response_format` are left entirely to the schema, including the meaning of the ten-value kind enum. Useful partial compensation, not full.

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 states the concrete outcome ('an app's ref from its name, its publisher, a brand it works with or what it does') and the result shape ('one row per app, best match first'), which is more actionable than a bare verb+resource. It is clearly a lookup/search over app listings and is distinguishable from ranking siblings. The only minor gap is that it frames the tool as a situation ('Use this when you need...') rather than stating 'Searches app listings' outright.

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

Usage Guidelines5/5

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

It gives an explicit positive trigger with concrete query examples ('create jira ticket'), plus a negative case ('Do not use for popularity or rankings') routed to a named alternative (charts_get). That is the when / when-not / alternative triad the dimension asks for, and it is the part of the definition an agent is most likely to act on.

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