IA Selecta

Submit a new AI tool

submit_tool

Submit a new AI tool to IA Selecta on behalf of its maker. Creates a draft listing (not yet public) and returns a claimUrl the maker must visit to sign up and claim/publish it. Call this only when a user explicitly wants to list their own tool — never to submit a tool on someone else's behalf without their email. Rate-limited globally to 5 submissions per hour. Supply tagline, problemSolved, logoUrl and imageUrls whenever you can: they are what make the published listing look like a real product page rather than a stub.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The tool's https homepage URL.
`name`	Yes	The tool's name.
`email`	Yes	The maker's email — used to claim the listing on signup.
`logoUrl`	No	https URL of the tool's logo. We copy it to our own storage — we never hotlink the maker's host.
`tagline`	No	One line shown on every card (max 60 chars). Supply it — without one we fall back to a truncated description.
`xHandle`	No	X/Twitter handle, without the @.
`category`	Yes	Category slug, e.g. 'agents', 'writing', 'coding', 'design', 'marketing', 'productivity', 'video', 'analytics'.
`imageUrls`	No	Up to 5 https screenshot URLs, best first. Copied to our own storage. Without any, the listing shows a generated placeholder card instead of a real screenshot.
`description`	Yes	A description of the tool (40-1000 chars).
`problemSolved`	No	What problem the tool solves, in the maker's words (max 160 chars). Rendered as its own block on the listing page.
`xHandleIsFounder`	No	True when the handle is the founder's personal account rather than the product's.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`error`	No
`claimUrl`	No	Where the maker signs up to claim the DRAFT. Present only when ok is true.

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already indicate a write operation, but the description adds crucial behavioral details: the listing is a draft (not public), the maker must claim it via claimUrl, and logo/image URLs are copied to IA Selecta's own storage. No contradictions with annotations.

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

Conciseness5/5

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

Four sentences, each packed with value: purpose, usage condition, rate limit, and param guidance. No fluff; ideas are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters and an output schema, the description effectively covers purpose, usage, behavior, and key parameter guidance. It doesn't need to detail return values since an output schema exists, making it complete for the agent's needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond by explicitly advising to supply tagline, problemSolved, logoUrl, and imageUrls for better listing quality, adding semantic value to optional parameters.

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 description clearly states what the tool does: submits a new AI tool on behalf of its maker, creates a draft listing, and returns a claimUrl. It distinguishes itself from sibling tools (get_tool, search_tools, etc.) by focusing on creation rather than retrieval or payment.

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?

Explicitly states when to call it ('only when a user explicitly wants to list their own tool') and when not to ('never to submit a tool on someone else's behalf without their email'). Also discloses the global rate limit of 5 submissions per hour, providing essential operational guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All IA Selecta tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools are clearly distinct: create_checkout, get_tool, list_alternatives, list_offers, search_tools, and submit_tool serve different purposes. However, list_alternatives and search_tools could be confused when searching for alternatives, but their descriptions clarify the target types (well-known tool slug vs. free-text query).

Naming Consistency4/5

Tool names follow a fairly consistent verb_noun pattern: create_checkout, get_tool, list_alternatives, list_offers, search_tools, submit_tool. The only minor deviation is that get_tool is singular while list_* are plural, but this is not a significant inconsistency.

Tool Count5/5

6 tools is well-scoped for a marketplace/directory server with search, detail retrieval, alternatives, paid promotions, and submission. Each tool serves a necessary function without redundancy or bloat.

Completeness4/5

The core workflows are covered: search and view details, list and purchase add-ons, and submit a listing. Minor gaps exist—no update/delete for listings or offers, and no way to manage claims—but these are administrative features outside the main agent use case.

Resources

Need Help?