Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket markets

polymarket_markets_list
Read-onlyIdempotent

List Polymarket markets by volume, liquidity, tag, or IDs with prices and rules; filter by status, volume, or liquidity and paginate with a cursor.

Instructions

List Polymarket markets by volume, liquidity, tag or ids, with prices and rules. Optional inputs: status, tagId, sort, ascending, minVolume and 9 more. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_markets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field. Default: `volume`.
limitNoItems per page, 1–100. Default: 50.
tagIdNoOnly markets with this tag id. Find ids with the tags list.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
localeNoTranslate titles and market questions into this language. Descriptions stay in English.
statusNoWhich markets to list: `open` (default) or `closed`. When you filter by `conditionIds` or `tokenIds` and omit this, open and closed markets are both searched.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
tokenIdsNoOnly the markets these outcome tokens belong to, up to 30. Repeat the parameter or separate ids with commas. For more ids use the batch endpoint.
ascendingNoSort from smallest to largest. Default: false (largest first).
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
maxVolumeNoOnly markets with at most this much volume (US dollars).
minVolumeNoOnly markets with at least this much volume (US dollars).
conditionIdsNoOnly these markets, by condition id, up to 50. Repeat the parameter or separate ids with commas. For more ids use the batch endpoint.
maxLiquidityNoOnly markets with at most this much liquidity.
minLiquidityNoOnly markets with at least this much liquidity.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
sportsMarketTypeNoOnly sports markets of this kind, such as `moneyline`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds modest value by saying results include prices and rules and that pagination uses a cursor, but it omits rate limits, page size defaults, and what an empty result looks like.

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?

Two sentences, front-loaded with the core action and filter scope, then a short note on pagination. Minor waste in the vague "and 9 more" enumeration, which conveys little an agent can act on.

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 17 parameters fully described in schema and no output schema, the description supplies the missing shape of the return value (a list of markets with prices and rules) and the cursor-based pagination rule. That is close to complete for a filtered-list endpoint, though the unusual required context/llm_model parameters are never acknowledged.

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 100%, so every parameter including status, tagId, sort, cursor and the required context/llm_model is documented in the schema. The description's parameter list ("status, tagId, sort, ascending, minVolume and 9 more") only restates a subset and adds no syntactic or semantic detail beyond it.

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 names a specific verb and resource ("List Polymarket markets") and states the filter dimensions (volume, liquidity, tag, ids) plus what each item contains (prices and rules). This separates it from single-market siblings like polymarket_market_get, though it never names a sibling explicitly.

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 the filter set and by "use cursor when paginated," and the schema's tagId note points to the tags list. But the description never states when to prefer this over polymarket_events_list, polymarket_markets_batch_get, or polymarket_market_get, so the agent must infer routing from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools