Skip to main content
Glama

Relaunch a listing

toolfound_relaunch
Idempotent

Relaunch an already-launched Toolfound listing: same listing, same URL, a new launch date shown alongside the old one. Relaunch requires a fresh verified-owner session, so this anonymous MCP transport reports the eligibility result but directs owners to the dashboard to authorize the write.

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": {
      "slug": "<slug>",
      "email": "<email>",
      "note": "<note>"
    },
    "name": "toolfound_relaunch"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesRequired: one line about what changed since the original launch (10-200 characters). Shown publicly on the listing page.
slugYesSlug of the listing to relaunch.
emailYesClaimed-owner email. The relaunch must still be authorized from its verified dashboard session.
requested_launch_dateNoPreferred new launch date, YYYY-MM-DD, within the next 180 days. Use toolfound_get_launch_calendar to find open featured seats. Falls back to the earliest open day if omitted or full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Must match the claimed-owner email or the email that verified the original submission: this is the ownership check, there is no separate verification step."New value: +"Claimed-owner email. The relaunch must still be authorized from its verified dashboard session."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the non-obvious runtime behavior: over this anonymous transport the call only reports eligibility and directs the owner to the dashboard to authorize the actual write. It also confirms the non-destructive, idempotent outcome (same listing and URL, old date preserved alongside the new), which is exactly the context an agent cannot get from the annotation flags alone.

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?

Two tight sentences with zero redundancy: the first front-loads what the tool does and its visible effect, the second front-loads the authorization caveat that determines whether the call can succeed. Nothing repeats the schema or the title.

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

Completeness4/5

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

For a four-parameter tool with full schema coverage and no output schema, the description covers the essential behavior and the transport limitation. The remaining gap is that it does not characterize the returned eligibility result (e.g., what fields or states come back, or what happens when the owner is ineligible), which the agent must discover at call time.

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?

Schema coverage is 100%, so the schema already documents slug, email, note, and requested_launch_date in detail, including the calendar-sibling hint and fallback behavior. The description adds only the high-level 'new launch date shown alongside the old one' framing and does not restate or extend parameter-level meaning, so the baseline 3 applies.

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 gives a specific verb (relaunch) and resource (an already-launched Toolfound listing) and states the concrete effect: same listing, same URL, a new launch date shown alongside the old one. The 'already-launched' qualifier implicitly separates it from submission-style siblings, but it never names a sibling such as toolfound_relaunch_decision or toolfound_submit_product outright.

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

Usage Guidelines4/5

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

It clearly states the precondition (the listing must already be launched) and the session requirement (a fresh verified-owner session), and it effectively tells the agent when this call will NOT complete the write by routing owners to the dashboard. What is missing is an explicit statement of the alternative to call when the listing is not yet launched or when the owner wants the write done through MCP.

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