Edit a tool
- Go to the dashboard.
- Open your tool from the list.
- Use the edit form to update any field.
- Click Save changes.
Fields reference
Tool image
Upload an image for your tool such as a logo or icon. It appears on tool cards and detail pages.Name
The display name of your tool. Required. Maximum 255 characters.Slug URL
The URL-friendly identifier for your tool. It appears asuseagents.site/t/your-slug.
- Must be at least 3 characters
- Must be unique across the registry
- Auto-generated from the name by default, but you can override it
Tagline
A one-sentence summary shown on tool cards. Recommended length: 10 to 160 characters.- Keep it concise and human-readable
- Focus on what the tool does and who it is for
- Example: “Agent-ready billing API for SaaS apps.”
Agent description
Describe what your tool does, the problem it solves, and how agents should use it. Maximum 500 characters.- Focus on functionality and integrations, not marketing copy
- Help agents understand when and how to recommend the tool
Links
| Field | Description |
|---|---|
| Website | Your tool’s homepage |
| Repo URL | GitHub or other source repository |
| Docs URL | Documentation link |
Tags
Add keywords that describe features, use cases, or technical capabilities. Avoid repeating categories.- Maximum 15 tags
- Maximum 30 characters per tag
- Tags are lowercased automatically
Categorization
| Field | Description |
|---|---|
| Categories | For example Authentication, CLI, SDK, API |
| Languages | For example TypeScript, Python, Go |
| Frameworks | For example React, Next.js |
Validation rules
- Tagline: 10 to 160 characters
- Agent Description: maximum 500 characters
- Slug: minimum 3 characters and unique
- Tags: maximum 15 tags, 30 characters each
- Links: must be valid URLs when provided
Best practices
- Lead with the tool’s actual capability, not generic praise.
- Describe integration points, supported languages, and common use cases.
- Use specific categories and tags instead of broad labels.
- Prefer canonical docs and repository URLs over marketing pages when possible.
Review before saving
- Check that the slug is stable and readable.
- Make sure the description explains what the tool does, not just why it is great.
- Keep categories, tags, languages, and frameworks aligned with the real integration surface.
Next steps
- Reviewing Changes to inspect draft changes
- Publishing & Deployments to make updates live