Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Swagger: Search APIs and Domains

swagger_search_apis_and_domains
Read-onlyIdempotent

Search SwaggerHub Registry for APIs and domains by name, description, tag, owner, or specification type. Filter results by state, sort order, and paginate through listings.

Instructions

Search for APIs and Domains in SwaggerHub Registry using the comprehensive /specs endpoint and retrieve metadata including owner, name, description, summary, version, and specification.

Toolset: Registry API

Parameters:

  • query (string): Search query to filter APIs by name, description, or content

  • state (enum): Filter APIs by publication state - ALL (default), PUBLISHED, or UNPUBLISHED

  • tag (string): Filter APIs by tag

  • offset (number): Offset for pagination (0-based, default 0)

  • limit (number): Number of results per page (1-100, default 20)

  • sort (enum): Sort field - NAME, UPDATED, or CREATED (default NAME)

  • order (enum): Sort order - ASC or DESC (default ASC)

  • owner (string): Filter APIs by owner (organization or user)

  • specType (enum): Filter by specification type - API or DOMAIN (default all types)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter APIs by tag
sortNoSort field - NAME, UPDATED, or CREATED (default NAME)
limitNoNumber of results per page (1-100, default 20)
orderNoSort order - ASC or DESC (default ASC)
ownerNoFilter APIs by owner (organization or user)
queryNoSearch query to filter APIs by name, description, or content
stateNoFilter APIs by publication state - ALL (default), PUBLISHED, or UNPUBLISHED
offsetNoOffset for pagination (0-based, default 0)
specTypeNoFilter by specification type - API or DOMAIN (default all types)
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds that it retrieves metadata via the /specs endpoint, but no additional behavioral traits like pagination behavior or auth requirements. It does not contradict annotations.

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 well-structured with a clear purpose sentence followed by a parameter list. It is front-loaded and efficient, though the parameter list is somewhat redundant with the schema.

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?

The description includes what metadata is returned, but lacks details on pagination (e.g., how offset/limit affect response) and no output schema. For a search tool with 9 parameters, this is adequate but could be more complete.

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 coverage is 100%, so baseline is 3. The description lists parameters with descriptions that are essentially identical to the schema, adding no extra semantic value.

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

Purpose5/5

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

The description clearly states 'Search for APIs and Domains' with specific verb and resource, and lists the metadata retrieved. It distinguishes from sibling tools as the only search tool in the swagger family.

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

Usage Guidelines4/5

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

The description clearly conveys when to use this tool (searching APIs/domains), but does not explicitly mention when not to use or alternative tools. However, sibling tools are distinct, so usage context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartBear/smartbear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server