Skip to main content
Glama

List an AI tool

submit_listing

Submit an AI tool for the list. Free listings wait for review. For fasttrack and featured you get checkoutUrl: give it to the person, who pays on Stripe.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan": "<plan>",
      "name": "<name>",
      "url": "<url>",
      "category": "<category>",
      "tagline": "<tagline>",
      "email": "<email>"
    },
    "name": "submit_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe tool's website
nameYes
planYes
emailYesThe maker's email, for questions about the listing. Never shown.
logoUrlNoA link to the tool's logo (square PNG, SVG or JPEG). Without it we take the icon from the tool's site.
taglineYesOne line about the tool, no links
categoryYes
launchAtNoOnly for a tool that isn't out yet: its launch day (UTC), YYYY-MM-DD, up to six months ahead. It shows as upcoming until then.
descriptionNo
pricingModelNo
sharedPaymentTokenNoPay by card now, as the agent: a Stripe shared payment token (spt_...) granted to our seller profile (see get_plans) for at least the plan price in USD. Charged once; without it, paid plans return a checkoutUrl for a person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Beyond the annotations (write operation, non-idempotent, non-destructive), it usefully discloses that free submissions enter a review queue and that paid plans return a checkoutUrl. However, it ignores the sharedPaymentToken flow that lets the agent pay directly, creating tension with the schema, and says nothing about duplicate submissions or what the free path returns.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action and plan behavior. The phrasing 'give it to the person, who pays on Stripe' is informal but compact; nothing is padded.

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

Completeness3/5

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

For a 6-required-parameter mutation tool with no output schema and 55% schema coverage, the description covers the headline outcome but not the full call contract: no mention of what a successful free submission returns, no auth/permission notes, and no reconciliation of checkoutUrl versus agent-side payment. It is adequate but leaves real gaps.

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?

With 55% schema coverage across 11 parameters, the description should compensate more than it does. It adds meaningful semantics for the 'plan' enum (free vs. paid outcomes, checkoutUrl) but says nothing about launchAt, logoUrl, pricingModel, tagline, or the payment token, leaving several parameters explained only by the schema or not at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Submit an AI tool for the list'), which is distinct from siblings such as check_listing or get_tool. It does not explicitly name an alternative tool, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives partial routing guidance by explaining the plan-dependent outcome: free listings wait for review, while fasttrack/featured yield a checkoutUrl to hand to a paying person. It never says when to use this versus check_listing (e.g., after submitting, check status), and it omits the agent-payment path described in the schema.

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.

Resources