Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Marketplace

list_marketplace
Read-onlyIdempotent

Browse aftermarket domains for sale on Porkbun. Filter listings by SLD substring, TLD, or length, and sort by price, domain, or SLD length.

Instructions

Browse domains for sale on the Porkbun marketplace (aftermarket — domains owned by other users, not new registrations). Returns each listing's domain, TLD, SLD length, price (in USD), and listing date.

Filters (all optional, server-side, mirroring the porkbun.com/marketplace UI):

  • query: SLD substring match. Multi-word queries: prefix a word with - to exclude it (e.g. "ai -test" matches SLDs containing 'ai' but not 'test').

  • tlds: limit to a list of TLDs (without the leading dot).

  • sld_length_min, sld_length_max: SLD character length bounds.

  • sort_name: domain | tld | price | sld_length.

  • sort_direction: asc | desc.

When any filter is set, server returns up to 1000 matching listings. With no filters, supports raw pagination via start / limit (max 5000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldsNoLimit to these TLDs (no leading dot). Example: `['com', 'io', 'ai']`.
limitNoPage size (no-filter mode only). Default 1000, max 5000.
queryNoSLD substring search. Use `-word` to exclude. Example: `'ai -test'`.
startNoPagination offset (no-filter mode only). Default 0.
sort_nameNoSort field. Default: `sld_length` asc when query is set, else `create_date` desc.
sld_length_maxNoMaximum SLD character length.
sld_length_minNoMinimum SLD character length.
sort_directionNoSort direction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: server-side filtering, a 1000-result cap in filter mode, and a 5000 max page size in no-filter mode. No auth or rate-limit disclosure, hence not 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.

Conciseness4/5

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

Front-loaded purpose sentence followed by a return-value list and a scannable bullet list of filters; each element earns its place. Slight redundancy with the schema's parameter descriptions keeps it from a 5.

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

Completeness5/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 steps in to enumerate returned fields (domain, TLD, SLD length, price, listing date) and the pagination/cap behavior, which is everything an agent needs to invoke and interpret results correctly.

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 coverage is 100%, so the baseline is 3, but the description goes further by spelling out the `-word` exclusion syntax and the mode-conditional semantics of filtering vs pagination that the schema only hints at. It largely mirrors the schema's own parameter descriptions, so it doesn't fully distinguish itself.

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?

Specific verb + resource ('browse domains for sale on the Porkbun marketplace') with an explicit disambiguation from sibling flows: 'aftermarket — domains owned by other users, not new registrations.' An agent can distinguish this from register_domain/list_domains without opening a schema.

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?

Clearly states the two operating modes (filtered search vs raw pagination) and the conditions that select them, plus the server-side filter semantics. It does not name a competing sibling tool or say when *not* to use it, so it stops short of a 5.

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

Deploy Server

Other Tools