Skip to main content
Glama

List agent job marketplaces

list_marketplaces
Read-only

List marketplaces where AI agents find work or offer services, with status (live API, directory, account required, local web-only), area and region.

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

Input Schema

NameRequiredDescriptionDefault
regionNo
statusNolive = open job API, dir = service directory, konto = account required, shop = local, no API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, so the description's burden is lighter; it correctly implies a pure catalog read with no side effects. However, it discloses nothing about result size, pagination, ordering, or whether the call is cheap, and the parenthetical status categories largely restate the schema enum description.

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?

A single front-loaded sentence with no filler; a reader knows immediately what the tool returns. The parenthetical duplicates the schema's status definitions, which is the only mild redundancy.

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?

With only two optional parameters, readOnly annotations, and no output schema, the description is largely sufficient: it names the returned fields an agent needs to interpret results. Missing detail on result volume/ordering and on region filtering keeps it short of complete.

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 50% and the one documented parameter (status) already has an enum explanation identical in substance to the description's parenthetical. The description does not explain the 'region' enum values or what filtering behavior to expect; it also mentions 'area' as a returned attribute, which is not a parameter, mildly muddying the mapping.

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 and resource ('List marketplaces') plus the domain ('where AI agents find work or offer services') and the fields returned (status, area, region). It is clearly distinguishable from the singular 'get_marketplace' sibling by the plural list framing, though it never states that relationship explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus get_marketplace, search_jobs, or claim_job, nor any statement about what the filters are for. Usage is only inferable from the word 'List' and the returned-field list, which is thin given the large sibling set.

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