List published AI prompt products on PromptBase.art marketplace. Returns slug, title, price, category, model, rating, salesCount, short description and the /marketplace/ URL. Search/filter by optional query.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Optional keyword to filter by title/description | |
| limit | No | Max results (1-50, default 20) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full responsibility for behavioral disclosure. It does state what the tool returns and that it filters by an optional query, but it does not mention ordering, pagination behavior, whether unpublished items are ever included, or any access constraints. It is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. It front-loads the core action, then provides return-value detail, and closes with filter behavior. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, enumerating the returned fields is valuable, and the description covers the essential behavior for a simple list tool with two optional parameters. It is slightly incomplete regarding pagination and ordering, but not to a degree that would prevent correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters with 100% coverage: q filters by title/description and limit sets max results. The description only echoes this with 'Search/filter by optional query,' adding no new meaning beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'List published AI prompt products on PromptBase.art marketplace.' It also lists the exact return fields and URL pattern, and clearly differentiates from the sibling get_prompt by indicating this is a multi-result listing/search operation rather than a single-item fetch.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use case is clear: search or browse the marketplace with an optional query. It does not explicitly name get_prompt as the alternative for retrieving a single prompt, but the listing vs. retrieval distinction is strongly implied by the description and the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.