Skip to main content
Glama

Search sites to submit a product to

search_sites
Read-onlyIdempotent

List launch platforms, directories, communities, newsletters, press and review sites that take product submissions, highest Ahrefs Domain Rating first. Every filter is optional; combine them to narrow the list.

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

Input Schema

NameRequiredDescriptionDefault
qNoPart of the site's name or domain, e.g. hunt or betalist
typeNoKind of site
limitNoSites per page (default 25)
nicheNoProducts the site is for. general sites take any product
priceNofree: free to list, including sites with paid options. free_without_backlink: free without having to link back to them. without_backlink: never asks you to link back to them, free or paid. paid: paid only
offsetNoSites to skip, from next_offset of the previous page
backlinkNoThe link the product gets: dofollow helps SEO
exposureNofeatured_to_audience: shown on their homepage, newsletter or social. depends_on_votes: visibility depends on upvotes. listing_only: a listing page, little promotion
acceptanceNoeveryone: every product that fits. reviewed: most get in. selective: only a few are picked

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / price / description
      Previous value: -"free: free to list, including sites with paid options. free_without_backlink: free without having to link back to them. paid: paid only"New value: +"free: free to list, including sites with paid options. free_without_backlink: free without having to link back to them. without_backlink: never asks you to link back to them, free or paid. paid: paid only"
    • changedInput schema / properties / price / enum
      Previous value: -[
      -  "free",
      -  "free_without_backlink",
      -  "paid"
      -]New value: +[
      +  "free",
      +  "free_without_backlink",
      +  "without_backlink",
      +  "paid"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world result set, so the safety profile needs no restating. The description adds genuinely new behavior: result ordering by Ahrefs Domain Rating descending and the fact that unfiltered calls return the broad list. It says nothing about result shape, page size defaults, or how many sites typically match, which for a 9-filter search tool would have been valuable.

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?

Two sentences, zero filler, and the front-loaded clause identifies the resource set and ordering before any caveats. Nothing to trim.

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?

For a read-only search tool with a fully documented 9-parameter schema and no output schema, the description covers purpose, ordering and filter behavior adequately. The remaining gaps (pagination expectations, result shape) are minor given the schema's offset description referencing next_offset. Naming get_site as the drill-down would have closed the loop.

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%, and the enum descriptions for price, exposure, acceptance and backlink are notably rich, so the schema carries the semantic load. The description only contributes the meta-rule that all filters are optional and combinable. Baseline 3 is appropriate.

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

Purpose4/5

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

The description gives a specific verb (list) plus the exact resource types (launch platforms, directories, communities, newsletters, press and review sites) and the submission-use scope, plus the sort order (Ahrefs Domain Rating descending). It is immediately clear what the tool returns. It never names the sibling get_site, so the list-vs-detail boundary is only implied by 'List'.

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?

'Every filter is optional; combine them to narrow the list' tells the agent how to drive the filters, which is real usage guidance. But there is no statement of when to reach for this versus get_site, nor when to stop filtering versus paging. Usage is implied rather than prescribed.

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