Skip to main content
Glama
Sign In
Official Porkbun MCP Server

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Marketplace

list_marketplace
Read-onlyIdempotent

Browse domains for sale on Porkbun Marketplace: names other Porkbun customers listed themselves, not new registrations. This is ONE aftermarket source; to find whether a taken name is for sale anywhere (Afternic, Sedo, Atom, NameBright…

Instructions

Browse domains for sale on Porkbun Marketplace: names other Porkbun customers listed themselves, not new registrations. This is ONE aftermarket source; to find whether a taken name is for sale anywhere (Afternic, Sedo, Atom, NameBright, DAX and Porkbun Marketplace together), use search_aftermarket. 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

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.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, so the bar is lower. The description adds genuinely useful operational detail beyond them: a 1000-result cap whenever any filter is set, versus raw pagination capped at 5000 in no-filter mode, plus an enumeration of returned fields. It omits auth/rate-limit context, so not quite 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?

Front-loaded with purpose and sibling routing in the opening sentence, then a compact bulleted filter list and a pagination note. For an 8-parameter tool, every sentence earns its place and the structure is easy to scan.

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 compensates by naming the returned fields (domain, TLD, SLD length, price, listing date). Combined with filter semantics, pagination modes, and result caps, an agent has everything needed to call it correctly.

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 100%, so the schema already documents `tlds`, `query` exclusion syntax, `start`/`limit`, `sort_name` defaults and enums. The description's filter list largely restates this rather than adding new syntax or constraints, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Browse domains for sale on Porkbun Marketplace') and immediately narrows scope ('names other Porkbun customers listed themselves, not new registrations'). It explicitly distinguishes itself from the sibling `search_aftermarket`, so an agent can route between them 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 Guidelines5/5

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

Gives explicit when-to-use and when-to-use-something-else guidance: 'This is ONE aftermarket source; to find whether a taken name is for sale anywhere ... use `search_aftermarket`.' It also notes the filters mirror the porkbun.com/marketplace UI, which anchors the mental model.

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