Skip to main content
Glama

Find earning opportunities

find_opportunities
Read-only

Browse unclaimed drafts from active campaigns the connected user can earn from — the public network AND the private spaces (distribution squads) the user is a member of, in one list, newest first. To see ONE space, pass space_id: never conclude a space has no drafts from the unfiltered list, because its drafts can be past the first page. An item from a space carries campaign.space (id, name): say which space it is from, and that it pays Stars inside that space. Each item is a real social post plus a pre-drafted text, with the platform it lives on (X, Reddit, YouTube, LinkedIn) and an actionType — reply (post it as a reply under the target post) or quote (X only: post it as a QUOTE of the target post, the text above the quoted post, from the user's own account). Free, read-only. Flow: the user picks an opportunity → call hold_opportunity on it (a 10-minute hold so no one else posts the same draft; one hold at a time) → the user edits and approves the text and posts it from their own account → call submit_participation with the URL of what they posted. Drafts other members are holding are not listed; the user's own live hold carries heldUntil. The user needs that platform's handle linked on their ProductClank profile for the reward to be attributable. Likes and reposts are proved with a screenshot and stay in the web app (app.productclank.com/feed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25
offsetNo
space_idNoOnly this private space's drafts (space_id from join_space, or campaign.space.id on an item). Use it whenever the user asks about ONE space or squad: the unfiltered list is newest first across everything, so a space's older drafts can be past the first page.
campaign_idNoRestrict to one campaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / space_id
      Added value: +{
      +  "description": "Only this private space's drafts (space_id from join_space, or campaign.space.id on an item). Use it whenever the user asks about ONE space or squad: the unfiltered list is newest first across everything, so a space's older drafts can be past the first page.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / action_type
      Removed value: -{
      -  "enum": [
      -    "reply",
      -    "like",
      -    "repost"
      -  ],
      -  "type": "string"
      -}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare read-only and closed-world; the description adds substantial behavior beyond that — newest-first ordering, page-depth caveat, exclusion of drafts other members are holding, the user's own hold surfacing as heldUntil, and the platform-handle prerequisite for reward attribution. It also flags which actions (likes/reposts) are out of scope and where they live.

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 purpose and scope before the flow and caveats, and nearly every sentence carries operational information. It is dense and long for a list tool, with the platform/actionType and flow passages bordering on over-packed, but little is genuinely disposable.

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?

There is no output schema, and the description compensates by describing item shape (campaign.space with id/name, platform values, actionType semantics for reply vs quote) and the hold/submit lifecycle. Nothing an agent needs to interpret results or act next is missing.

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 75%, so the schema already documents space_id and campaign_id. The description adds real meaning beyond it by explaining why space_id matters (pagination risk in the unfiltered list) and where the id comes from, though campaign_id, limit and offset get no treatment in the prose.

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?

States a concrete verb and resource ('Browse unclaimed drafts from active campaigns'), scopes it precisely (public network plus the user's private spaces, newest first), and implicitly separates itself from campaign-browsing siblings by focusing on claimable drafts. An agent can tell what it returns without opening the 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 guidance: pass space_id when the user asks about ONE space, and a direct warning not to conclude a space is empty from the unfiltered list. It also names the downstream tools (hold_opportunity, submit_participation) and the full user flow, so routing is unambiguous.

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.