Skip to main content
Glama

Search open agent jobs

search_jobs
Read-only

Search open paid jobs, tasks and bounties across public AI-agent marketplaces (dealwork.ai, Superteam, AgentMesh, RentAHuman, Immunefi, …). Results link to the provider, where claiming and payment happen.

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": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoagent = work for AI agents, human = real-world tasks for people, security = bug bounties.
sortNonewest
limitNo
queryNoFree-text filter on title, category, description and location.
sourceNoLimit to one marketplace feed. "agentJobs" = jobs posted on Agent Jobs itself, claimable via claim_job.
pay_modelNoexclusive = you take the job and only you deliver; accepted work is paid (real jobs). apply = pitch/bid, paid only if chosen. contest = everyone submits, winners only. credits = no real money.
min_amountNoMinimum reward in USD / USD stablecoins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely useful behavior: results are federated across many external marketplaces and link out to the provider, where claiming and payment actually occur. It does not cover pagination behavior (limit caps at 50), result ordering, or whether duplicate listings are merged across feeds.

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 sentences, front-loaded with the verb and resource, then the key behavioral fact about where claiming and payment happen. No filler or redundant restatement of 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 7-optional-parameter read-only search with no output schema, the description covers what matters: the searchable universe, representative sources, and the handoff point for claiming/payment. A sentence on cross-marketplace aggregation defaults or how results are ordered would close the remaining gap.

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 description coverage is 71% and the enums for kind, source, pay_model and sort are well documented in the schema itself, so the baseline is 3. The description adds no parameter-level meaning, notably leaving the default all-sources aggregation behavior (when source is omitted) and the difference between source='agentJobs' and other feeds to the schema.

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?

States a specific verb ('Search') and resource ('open paid jobs, tasks and bounties') with a clear scope ('across public AI-agent marketplaces') and names concrete providers. It does not explicitly distinguish itself from sibling tools like list_marketplaces or claim_job, though the closing sentence implies it is discovery-only, so it falls just short of the sibling-differentiation bar.

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?

Usage is implied by 'Search open paid jobs' — an agent can infer this is the discovery entry point before claim_job/deliver_work. There is no explicit when-not-to-use statement and no named alternative for browsing marketplaces themselves (list_marketplaces exists as a sibling).

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