Uneed

OpenQuok MCP examples for Uneed directory launch — profiles, uneed variants, listing readiness, and cached directory SEO.

3 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start your free trial

Directory launch quick reference

Property	Value
Directory site key	uneed
Submit host	uneed.best (you click submit on Uneed — OpenQuok autofills)
Integration docs	Uneed directory integration
Tools reference	Directory launch tools

Not schedulePostTool

These tools manage product profiles and launch readiness. They do not publish to Uneed for you. After directoryVariantsEnsure tailors copy, use the browser extension to open uneed.best and submit.

Plan capabilities

Directory launch tools need directory_launch_enabled on the workspace plan. Directory SEO tools need directory_seo_enabled.

List Uneed destinations

Which Uneed launch paths are in the OpenQuok catalog — join the line, paid launch, maker profile?

The agent calls directoryDestinationsList and filters rows where the provider slug is uneed.

Main profile and Uneed variant

Create or open my Uneed-tailored product profile from my main business profile, and tell me how similar it is to the main profile.

Alternate wording (same tool chain):

List my main product profile, ensure a Uneed variant exists, and tell me how similar the variant is to the main profile.

The agent should:

Call directoryProfilesList with mainOnly: true and read productProfileId from the first row.
Call directoryVariantsEnsure with that id and directorySiteKey: uneed.

{
  "mainProductProfileId": "<main-product-profile-id>",
  "directorySiteKey": "uneed"
}

Idempotent variant

directoryVariantsEnsure returns the existing variant with created: false when one already exists for uneed.

Use directoryProfilesGet on the main or variant id when you need full profileData or maker/pricing fields.

Listing readiness before you open uneed.best

For my main product profile, show Uneed readiness — submission status and any missing fields.

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directoryListingSummary and reads the uneed destination row.

Update my Uneed variant with this maker bio and pricing copy.

Call directoryProfilesUpdate with the variant productProfileId and the fields to patch.

Logo and screenshots: logoUrl and profileData.gallery_urls — same as PeerPush; see Directory launch — logo and screenshots and MCP examples — PeerPush (logo and screenshots).

Submissions (read-only)

List directory submissions recorded for my main product profile.

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directorySubmissionsList.

Directory SEO (cached metrics)

What are my directory SEO ratings for my main profile, and when were they last checked?

{
  "productProfileId": "<main-product-profile-id>"
}

The agent calls directorySeoOverview. Read checkedAt on each metric and manualRefreshAvailableAt before directorySeoRefresh.

Add competitor domain rival.example to my directory SEO workspace and show history for the last 90 days.

The agent calls directorySeoCompetitorsAdd with domain and optional label, then directorySeoHistory with days: 90.

checkedAt

Domain rating and competitor metrics are cached. Responses include checkedAt and manualRefreshAvailableAt after directorySeoRefresh.

End-to-end workflow

Prepare my product for Uneed: ensure the uneed variant, show Uneed readiness on the listing summary, and give me the latest cached domain rating with checkedAt.

The agent chains directoryProfilesList → directoryVariantsEnsure (uneed) → directoryListingSummary → directorySeoOverview.