Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket events

polymarket_events_list
Read-onlyIdempotent

List Polymarket events filtered by volume, date, tag, status, or title, including each event's markets, so you can find and compare prediction markets for research or monitoring.

Instructions

List Polymarket events by volume, date, tag or title, with each event's markets. Optional inputs: status, tag, query, sort, ascending and 12 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_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly events with this tag: a tag id or slug.
sortNoSort field. Default: `volume`.
limitNoEvents per page, 1–25. Default: 20. Each event carries all of its markets and the busiest hold hundreds, so a page stays small. Use `cursor` for the next page.
queryNoWords to find in event titles. Titles are English, so search in English.
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 items to list: `open` (default), `closed` (ended or resolved) or `all`. `open` is Polymarket's own flag and can outlast the end date.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
featuredNoOnly events Polymarket features (true) or only those it does not (false).
seriesIdNoOnly events in this series.
ascendingNoSort from smallest to largest. Default: false (largest first).
endDateToNoOnly events ending on or before this date.
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 events with at most this much volume (US dollars).
minVolumeNoOnly events with at least this much volume (US dollars).
endDateFromNoOnly events ending on or after this date.
startDateToNoOnly events starting on or before this date.
minLiquidityNoOnly events with at least this much liquidity.
startDateFromNoOnly events starting on or after this date.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds useful context that each event carries all of its markets and that pagination uses a cursor, but it does not mention page-size limits, rate behavior, or what a truncated result looks like; most of that is left to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening clause is front-loaded and effective, but 'and 12 more' is a low-value enumeration that neither informs nor guides, and the cursor remark is terse enough to be ambiguous about which parameter it refers to.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter, paginated, open-world listing tool with no output schema, the description says notably little about return shape beyond 'a list' and 'each event's markets'. The schema carries most of the load, leaving the description adequate but not 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 description coverage is 100%, so every one of the 20 parameters is already documented with enums, ranges and defaults. The description merely restates a handful of them ('status, tag, query, sort, ascending and 12 more') without adding meaning, so the baseline of 3 applies.

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 Polymarket events') plus the axes it can be filtered/sorted by ('volume, date, tag or title') and notes that each event is returned with its markets. It does not distinguish the tool from close siblings such as polymarket_us_events_list, so it stops short of a 5.

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 list and by the pagination hint ('use cursor when paginated'), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for overlapping cases like US events.

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