Tools

Every tool is a thin wrapper over the same functions the REST API calls, so a result never depends on which transport asked for it.

At a glance

Tool	Auth	Input
search_products	None	query, category, limit, cursor
get_product	None	slug
list_launch_directories	None	limit
check_launch_readiness	None, 10 per hour	url
submit_product	Connection	url, plus optional listing fields
get_my_launches	Connection	None
connect_account	Not applicable	code (optional)

connect_account

The pairing helper. Called with no arguments it starts a pairing and returns the approval link. Called with a code it completes one. You normally never invoke it yourself, because submit_product and get_my_launches start pairing on their own when a session has no account attached, which is described in Authentication.

A sensible order to use them in

1. 1

   Look around

   search_products and get_product tell you what already exists in the category you are launching into, which is the fastest way to write a tagline that is not a duplicate of three others.

2. 2

   Audit before you write anything

   check_launch_readiness returns the reasons a listing gets rejected before a reviewer ever sees it, plus a suggested listing you can pass straight into the next step.

3. 3

   Open the draft

   submit_product creates it in draft status and hands back a link.

4. 4

   Track it

   get_my_launches reports status, plan, requested week, upvotes and impressions for everything you have submitted.

Errors

Tool failures use the same codes as the REST API: UNAUTHORIZED, FORBIDDEN, NOT_FOUND, BAD_REQUEST, TOO_MANY_REQUESTS and INTERNAL_SERVER_ERROR. See Errors.