Skip to main content
Glama

findagent_submit_for_review

Idempotent

WRITES: this is the tool that actually SUBMITS, and the draft enters human review. Not to be confused with findagent_submission_wizard, which only returns the next question to ask and changes nothing. Submit YOUR OWN draft listing for review — the final step that reaches full parity with the web submit wizard (set price, confirm originality + prohibited content, submit). Auto-detects whether the draft is built here (instructions, skills, actions) or carries code and finalizes it the same way the web wizard does: it flips your draft to pending_review (NOT published — an admin reviews it, and for an agent with code a security scan must pass, before it goes live). Pass agent (the slug or id of your draft, created via findagent_create_draft / findagent_create_code_draft), price_type/price_cents, the LLMs it targets, and BOTH confirmations. confirm_original + confirm_not_prohibited are YOUR attestation that this is your original work and avoids prohibited content (malware, illegal, or disallowed use) — both must be true, exactly like the web wizard's checkboxes. SLUG IS PERMANENT: the first time you call this WITHOUT confirm_slug it returns the exact final slug + a notice that the public URL can never change after publish; re-call it with confirm_slug set to that exact slug to acknowledge and proceed (this mirrors the web wizard's permanence confirm — you never lock a slug you didn't see).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llmsYesThe clients/LLMs this agent targets (at least one).
agentYesThe slug or id of YOUR draft (from findagent_create_draft / findagent_create_code_draft).
price_typeNoDefault free. "paid" requires price_cents (charged once Paddle is live).
price_centsNoRequired when price_type=paid: a positive integer of US cents, max 50000 ($500).
confirm_slugNoYour acknowledgement that the listing's public URL slug is PERMANENT after publish. Must exactly match the draft's slug. Call this tool WITHOUT it first to see the exact slug + permanence notice, then re-call with confirm_slug set to that slug to publish.
thumbnail_urlNoOptional. Accepted ONLY if already hosted on FindAgent assets; otherwise ignored (upload a thumbnail in the web wizard — off-site image URLs are not fetched).
confirm_originalYesRequired true — your attestation that this listing is your original work.
confirm_not_prohibitedYesRequired true — your attestation that it avoids prohibited content (no malware, illegal, or disallowed use).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNo
statusNo
accountNo
submittedNo
review_urlNo
instructionsNo
thumbnail_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnly/idempotent/destructive hints; the description goes well beyond them by disclosing that the state flips to pending_review rather than published, that an admin reviews it, that code-bearing agents must pass a security scan, that the slug is permanent and must be acknowledged, and that off-site thumbnail URLs are silently ignored. These are exactly the side effects and failure modes an agent needs before a mutating call.

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?

Front-loaded with the critical WRITES/SUBMITS signal and the sibling disambiguation, which is the right priority. The prose is dense and the permanence rule is stated twice, which costs a little, but nearly every sentence carries an actionable constraint.

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?

For an 8-parameter mutating tool with an output schema, the description covers the missing pieces: prerequisites and originating tools, the attestation semantics, the review/scan gate, and the slug-permanence protocol. An agent has everything needed to invoke it correctly on the first attempt.

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 the baseline is 3, but the description adds genuine meaning: it frames confirm_original/confirm_not_prohibited as the caller's own attestation (mirroring the web checkboxes) and explains the non-obvious confirm_slug handshake as a call-without-then-recall pattern. It does not restate the price/llms constraints in more depth than the schema already does.

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?

Opens with an explicit verb+resource ("the tool that actually SUBMITS, and the draft enters human review") and immediately distinguishes itself from findagent_submission_wizard by stating what that sibling does not do. An agent can route between the two without opening either schema.

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?

Gives explicit when-to-use (submit YOUR OWN draft as the final step), when-not-to-use (not the wizard, which only returns the next question), and names the exact creating tools (findagent_create_draft / findagent_create_code_draft). It also lays out the two-call confirm_slug sequence so the agent knows the invocation order before calling.

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