Skip to main content
Glama

Listing targets

listing_targets

The next directories to list the product on: free to list (or free on a condition, stated in the note), open to this kind of product, not already recorded as listed, ranked first by how often the AI answers to this product's own buyer questions cite them (citedForYou, from its latest visibility run), then by how often AI answers cite them across Shipfound's runs, each with where to submit. Review profiles only when asked for in include; launch boards (Product Hunt, DevHunt, Show HN, Indie Hackers) are launch_targets. Free. With marketplaces true, instead the MCP registries, plugin lists, extension stores and GitHub awesome lists the product fits and is not recorded on yet. Free.

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": "listing_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many; default 10
includeNoAlso review profiles (G2, Capterra) with "review". Launch boards are launch_targets; "launch" is kept for older plugins and adds nothing
marketplacesNoThe marketplaces and awesome lists instead of directories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include / description
      Previous value: -"Also launch platforms (Product Hunt) or review profiles (G2, Capterra)"New value: +"Also review profiles (G2, Capterra) with \"review\". Launch boards are launch_targets; \"launch\" is kept for older plugins and adds nothing"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations only declare non-destructive, closed-world, but notably readOnlyHint=false on what reads as a read operation; the description never addresses that, though it also never claims a write, so there is no direct contradiction. It does add real behavioral context beyond annotations: results are filtered to free-to-list and not-yet-listed entries, ranked by citedForYou then Shipfound-wide citation frequency, and each entry includes a submission location. Cost transparency is limited to a repeated 'Free.' with no indication of result size or pagination beyond the count cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

All sentences carry information, but it is one long run-on with nested parentheticals ('ranked first by how often the AI answers to this product's own buyer questions cite them (citedForYou, from its latest visibility run)') that is hard to parse. 'Free.' is duplicated at the end and 'free to list (or free on a condition, stated in the note)' repeats the same idea.

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 does the work of describing the return shape: ranked targets each with where to submit, plus the ranking signals. It is complete enough to call correctly, with the only gap being whether the readOnlyHint=false annotation implies side effects.

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 baseline is 3; the description mostly restates the schema (review via include, marketplaces switching modes) with only slight added concreteness about what marketplaces returns (MCP registries, plugin lists, extension stores, GitHub awesome lists). It adds no syntax or default guidance for count.

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?

The opening clause states a specific resource and scope — 'The next directories to list the product on' — followed by the exclusion criteria (free, open to this kind of product, not already listed). It also explicitly names the sibling it is not (launch boards go to launch_targets) and the alternate mode (marketplaces).

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?

It gives explicit when-to-use routing: review profiles only when 'review' is requested in include, launch boards belong to launch_targets, and marketplaces=true switches to registries/stores/awesome lists. That is when/when-not/alternative coverage in one pass.

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.