meta-agent-tools

list_listings

Public mosaic of live MCP servers, skills and plugins.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Free text over the name, the tagline and the description. Kind, topic and transport words become filters.
`low`	No	`1` includes `low` listings in the result. Only valid together with `q`.
`kind`	No	Which kind of resource to fetch.
`sort`	No	Result order.	recent
`category`	No	Category declared by whoever published.
`interpret`	No	`0` disables query understanding and searches the raw string.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / interpret

Added value: +{
+  "description": "`0` disables query understanding and searches the raw string.",
+  "enum": [
+    "0"
+  ],
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Free text over the name, the tagline and the description."New value: +"Free text over the name, the tagline and the description. Kind, topic and transport words become filters."

Changed9 schema fields changedSep 6, 2026

addedInput schema / properties / category / description

Added value: +"Category declared by whoever published."

addedInput schema / properties / kind / description

Added value: +"Which kind of resource to fetch."

addedInput schema / properties / kind / enum

Added value: +[
+  "mcp",
+  "skill",
+  "plugin"
+]

addedInput schema / properties / low / description

Added value: +"`1` includes `low` listings in the result. Only valid together with `q`."

addedInput schema / properties / low / enum
```
Added value: +[
+  "1"
+]
```

addedInput schema / properties / q / description

Added value: +"Free text over the name, the tagline and the description."

addedInput schema / properties / sort / default
```
Added value: +"recent"
```
addedInput schema / properties / sort / description
```
Added value: +"Result order."
```

addedInput schema / properties / sort / enum

Added value: +[
+  "recent",
+  "likes",
+  "visits"
+]

First observedSep 5, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. The description only states a 'public mosaic' without mentioning whether the operation is read-only, whether authentication is required, or whether pagination or rate limits apply. The name suggests a non-destructive list, but this is not explicit.

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

Conciseness3/5

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

The description is concise but overly metaphorical and under-specified. It is a single sentence that does not waste words, but it also fails to include key details such as the resource type being listed or how filters work. The structure is clean but sacrifices clarity.

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

Completeness2/5

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

The description lacks surrounding context: it does not explain the response format, the relationship to list_mcp_servers, when to use the 'kind' filter versus the generic 'q' search, or any limitations. While the parameter comments add context, the overall tool frame is incomplete for an agent to confidently select and invoke it.

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?

All six parameters have descriptive comments in the schema, covering their purpose and constraints (e.g., 'low' is only valid with 'q', 'interpret' disables query understanding). This exceeds the baseline and provides clear meaning for each field, though the parameters themselves are optional and open-ended.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Public mosaic of live MCP servers, skills and plugins' conveys a broad listing intent but uses a metaphor instead of a clear verb like 'list' or 'search'. It does not distinguish this tool from sibling list_mcp_servers, making the purpose somewhat ambiguous without relying on the name.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool compared to alternatives like list_mcp_servers, get_listing, or go_listing. There is no context about query parameters, filters, or typical scenarios, leaving the agent to infer usage from the parameter schema alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All meta-agent-tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.7/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but list_listings and list_mcp_servers overlap since both return listings, with the latter being a filtered subset. This minor ambiguity could cause occasional misselection.

Naming Consistency3/5

The majority of tools follow verb_noun snake_case (create_listing, get_listing, like_listing), but several are bare nouns (billing, contact, health) or compound nouns (api_index), breaking the consistent pattern and reducing predictability.

Tool Count5/5

12 tools is well-scoped for a registry server covering listings, comments, likes, billing, and health. Each tool has a clear purpose and the count feels neither thin nor bloated.

Completeness3/5

The listing lifecycle is incomplete: create, get, like, and list exist, but there is no update or delete for listings. Additionally, only list_comments is available—no create, edit, or delete for comments—creating notable workflow gaps.

Resources

Need Help?