Skip to main content
Glama

Submit by Hand

Search product directories

search_directories
Read-only

Search our checked list of live startup, SaaS, AI tool and general directories that accept product submissions. Free, no account needed. Each result has the submit URL, domain rating, pricing (free / freemium / paid), whether it needs an account, email confirmation, a captcha or a backlink, when we last checked it, and a step-by-step guide link where we have one. Highest domain rating first.

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_directories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, default 25.
queryNoPart of the directory name or domain.
min_drNoMinimum domain rating (Ahrefs DR, 0-100).
offsetNoSkip this many results (paging).
categoryNoOnly directories that list this kind of product. "general" = any product.
free_onlyNoOnly directories with a free way to submit (pricing free or freemium).
no_accountNoOnly directories that need no account.
no_captchaNoOnly directories without a captcha.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that entries are 'checked' and include a last-checked timestamp, that results are sorted by domain rating descending, and that access is free with no account. It does not mention pagination behavior, though the offset/limit parameters are documented in the schema.

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?

Two sentences, front-loaded with purpose, then a dense but relevant enumeration of returned fields. The field list is long but each item corresponds to something an agent would act on; nothing is filler.

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?

With no output schema, the description carries the burden of describing results and does so thoroughly, listing every returned attribute plus sort order. Combined with fully documented parameters, an agent has enough to call it correctly, though paging expectations are only covered by the schema.

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 the baseline is 3. The description indirectly explains what the filters target by enumerating result attributes (pricing tiers, account requirement, captcha, backlink), but it does not name or explain any filter parameter directly.

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 (Search) and resource (a checked list of live directories that accept product submissions), plus scope (startup, SaaS, AI tool, general). An agent can tell this apart from get_directory by name and purpose 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 Guidelines3/5

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

Usage is implied by the framing (find directories to submit a product to), and 'Free, no account needed' clarifies access. However, there is no explicit when-to-use/when-not guidance and no named alternative such as get_directory for fetching a single directory's details.

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.

Resources