Skip to main content
Glama

Launch directory matcher

toolfound_directory_matcher
Read-onlyIdempotent

Filter the dated launch-directory evidence by product fit, cost, format, and link policy. Use it when you are choosing where to list or launch a product and want a shortlist of directories that fit your product type, budget, listing format and backlink needs. Returns the matching directories from dated evidence with their recorded cost, format and link policy; it checks nothing live. Returns an evidence-bounded result and the canonical web tool URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segment": "<segment>",
      "cost": "<cost>",
      "launchModel": "<launchModel>",
      "dofollow": "<dofollow>"
    },
    "name": "toolfound_directory_matcher"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYesWhether getting listed costs money. free keeps directories with at least one free path, paid keeps those that only charge, unknown keeps those with no recorded price. any skips the filter.
segmentYesThe kind of product you are launching, used to keep only directories that accept that kind of product. Use any to skip this filter.
dofollowYesThe recorded policy on whether the directory's backlink to your site passes SEO value (a followed link). conditional means it depends on a rule such as a plan or a rank. unknown means not yet verified. any skips the filter.
launchModelYesHow the directory presents a listing: time-boxed rankings (daily, weekly, monthly), a permanent evergreen listing, a community post, a review site, a deal marketplace, a tool database or a newsletter feature. any skips the filter.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cost / description
      Added value: +"Whether getting listed costs money. free keeps directories with at least one free path, paid keeps those that only charge, unknown keeps those with no recorded price. any skips the filter."
    • addedInput schema / properties / dofollow / description
      Added value: +"The recorded policy on whether the directory's backlink to your site passes SEO value (a followed link). conditional means it depends on a rule such as a plan or a rank. unknown means not yet verified. any skips the filter."
    • addedInput schema / properties / launchModel / description
      Added value: +"How the directory presents a listing: time-boxed rankings (daily, weekly, monthly), a permanent evergreen listing, a community post, a review site, a deal marketplace, a tool database or a newsletter feature. any skips the filter."
    • addedInput schema / properties / segment / description
      Added value: +"The kind of product you are launching, used to keep only directories that accept that kind of product. Use any to skip this filter."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world and idempotent behavior, so the extra burden is light. The description earns credit by disclosing that results come from dated evidence, that it checks nothing live, and that the response is evidence-bounded plus a canonical tool URL — a staleness caveat the annotations cannot express.

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?

Three sentences, front-loaded with the filtering action and followed by the use case and the freshness caveat. There is mild redundancy between the facet list in sentence one and the restated list in sentence two, but the restatement usefully maps business terms to parameters.

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?

An output schema and rich annotations are present, so the description need not explain return values, and it correctly does not. Combined with the explicit 'checks nothing live' caveat, an agent has what it needs to call this correctly; only the absence of sibling routing keeps it from a 5.

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% and every parameter is a documented enum, so the schema already does the semantic work. The description restates the four facets in plain language (product fit, cost, format, link policy), which aids mapping but adds no filter syntax or edge-case detail beyond the schema.

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 states a specific verb (filter) and resource (dated launch-directory evidence) and enumerates the four facets it filters on: product fit, cost, format and link policy. This is clearly distinguishable from siblings like search_tools or find_by_task, though it does not explicitly name a competing alternative.

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?

It gives a clear use case: when choosing where to list or launch a product and you want a shortlist matching product type, budget, listing format and backlink needs. It stops short of stating when NOT to use it or naming a specific alternative tool for a different job.

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