Skip to main content
Glama

Search MCP servers and agent skills

search_listings
Read-onlyIdempotent

Search Kitbay's directory of MCP servers and agent skills by text, or browse by tool, category or AI client. Returns facts per listing (official, can change data, needs credentials, licence, last activity) and its Kitbay page. Needs a query, tool, category or client.

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

Input Schema

NameRequiredDescriptionDefault
toolNoTool slug or name, e.g. "figma"
typeNoOnly MCP servers or only agent skills
limitNoResults per page, 1-25 (default 10)
queryNoWords to search for, e.g. "figma" or "postgres read only"
clientNoAI client slug, e.g. "claude-code", "cursor"
cursorNonextCursor from the previous page
categoryNoCategory or capability slug from list_categories (e.g. "design-and-creative", "code-review")
officialNotrue: only listings the tool's vendor publishes
canChangeDataNoWhether it can create, change or delete data
needsCredentialsNoWhether it needs an API key or sign-in

Output Schema

NameRequiredDescriptionDefault
noteNo
totalYes
resultsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context about returned facts such as official status, data-change ability, credential needs, licence, and last activity, but it does not discuss pagination behavior or other operational details beyond what the schema provides.

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?

The description is three tight sentences with the primary search purpose front-loaded, followed by browsing options and the required input condition. Every sentence contributes useful information without repetition.

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?

Given the ten parameters, full schema description coverage, output schema, and annotations, the description is largely complete. It covers purpose, primary input constraint, and returned facts, though it omits explicit sibling-tool routing that would further reduce ambiguity.

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?

Schema description coverage is 100%, so the baseline would be 3. The description adds a meaningful cross-parameter constraint: at least one of query, tool, category, or client must be supplied, even though the schema marks zero parameters as required.

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 verb and resource: searching Kitbay's directory of MCP servers and agent skills. It also covers browsing by tool, category, or AI client, making the purpose clear without explicitly distinguishing it from siblings like get_listing or list_categories.

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?

It states that a query, tool, category, or client is needed, which gives implied usage guidance. However, it does not explain when to use this tool instead of get_listing, get_tool, or list_categories, nor does it name any exclusion conditions.

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.