Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket series

polymarket_series_list
Read-onlyIdempotent

List Polymarket event series such as league seasons and recurring markets, then filter by recurrence or closed status and paginate with a cursor for complete results.

Instructions

List Polymarket event series such as league seasons and recurring markets. Optional inputs: recurrence, closed, limit and cursor. 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_series_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–50. Default: 50.
closedNoOnly series that have ended (true) or are still running (false).
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
recurrenceNoOnly series that add an event on this schedule.
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

A3.5/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 the safety profile is fully covered by structured data. The description adds only that results are a list and that pagination uses a cursor — useful but thin, with no mention of rate limits, auth requirements, or how empty results appear.

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 short sentences, front-loaded with the purpose before the parameter and pagination notes. The enumeration of optional inputs is slightly redundant given full schema coverage, but nothing is padded or unclear.

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 seven-parameter read-only listing tool with no output schema, the description covers purpose, the existence of filters, and pagination behavior, which is close to sufficient. It could go further by describing the shape of a returned series or clarifying the relationship to the US-series and single-series siblings.

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 the required context and llm_model is already documented in the schema. The description merely names four optional inputs (recurrence, closed, limit, cursor) without adding semantics such as how recurrence values interact with closed, which is the baseline when the schema does the work.

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 and resource ("List Polymarket event series") and adds concrete examples of what a series is ("league seasons and recurring markets"), which is more than the title alone provides. It does not distinguish itself from the closely named sibling polymarket_us_series_list or from polymarket_series_get, leaving the agent to infer the boundary.

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 only implied by the purpose statement — an agent can reasonably deduce "call this to enumerate series." The only explicit guidance is mechanical ("use cursor when paginated"), with no statement about when to prefer polymarket_series_get, polymarket_us_series_list, or polymarket_events_list.

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