> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useagents.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding Your Tool

> Add your CLI, library, SDK, or API to the UseAgents registry so agents can discover and use it correctly.

Create a draft tool in UseAgents, fill in the metadata agents need, and publish it to the registry. Focus on accurate naming, descriptions, links, and categorization so agent builders can understand when to use your tool.

## Prerequisites

* An account at [useagents.site](https://useagents.site)
* An organization (created automatically when you sign up)
* A tool website, repository, or documentation link you can attach to the listing

## Step 1: Create a tool

1. Go to the [dashboard](https://useagents.site/dashboard) and click **Add Your Tool** (or **Add Tool**).
2. Enter the **name** and **slug** for your tool. The slug is the URL-friendly identifier (e.g. `my-auth-sdk`).
3. Optionally add an **image** URL for your tool's logo.

Your tool starts in **draft** status. It won't appear in the registry or search until you publish it.

## Step 2: Fill in metadata

Edit your tool to add the metadata agents use to discover and understand it. See [Editing Your Tool](/developers/editing-tools) for a full field reference, limits, and validation rules.

| Field                                     | Description                                                              |
| ----------------------------------------- | ------------------------------------------------------------------------ |
| **Name** / **Slug**                       | Display name and URL identifier                                          |
| **Tagline**                               | One-sentence summary on tool cards (10–160 characters)                   |
| **Description**                           | What the tool does and when agents should choose it (max 500 characters) |
| **Quickstart**                            | Per-language install command and usage code                              |
| **Input shape**                           | Parameters, types, required vs optional                                  |
| **Output shape**                          | Response shape agents should expect                                      |
| **Common pitfalls**                       | Gotchas not obvious from official docs                                   |
| **Tags**                                  | Up to 15 keywords for search (max 30 characters each)                    |
| **Categories**                            | e.g. Authentication, CLI, SDK, API (at least one for deploy)             |
| **Languages** / **Frameworks**            | Supported languages and frameworks                                       |
| **Website** / **Repo URL** / **Docs URL** | Supporting source links                                                  |

The more accurate and complete your metadata, the better agents can find and use your tool.

## Step 3: Review and publish

1. Review the draft content and confirm every link points to the canonical site, repo, or docs.
2. Check that the description explains what the tool does, not just marketing language.
3. Confirm the categories, languages, frameworks, and tags reflect the actual integration surface.
4. Publish the tool to make it live in the registry.

## Verify the result

After publishing:

1. Open the tool's public page in the registry.
2. Confirm the title, description, and links are correct.
3. Use the MCP server or search UI to verify the tool is discoverable for relevant queries.

## Next steps

* [Why Publish to UseAgents](/developers/philosophy) — Philosophy and design principles for listings
* [Reviewing Changes](/developers/changes) — Review your draft changes before deploying
* [Publishing & Deployments](/developers/publishing) — Deploy your tool to make it live in the registry