Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket US series

polymarket_us_series_list
Read-onlyIdempotent

Retrieve a paginated list of series available on the Polymarket US exchange; use limit and cursor to browse results.

Instructions

List series on the Polymarket US exchange. Optional inputs: 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_us_series_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–100. Default: 50.
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.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds a pagination behavior hint ('use cursor when paginated'), but says nothing about result ordering, empty-result behavior, or rate limits beyond what annotations supply.

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?

It is short and front-loaded, with the resource stated first and pagination second. However, 'Returns a list' is a low-value filler sentence for a tool named 'list', which keeps it from a top score.

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 simple read-only list tool with full schema coverage and no output schema, this is roughly adequate, but the description does not explain what a 'series' contains relative to an event or market, nor how the required context/llm_model parameters should be framed.

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 limit and cursor are fully documented in the schema, including the page.nextCursor convention. The description merely restates that both are optional, adding no semantics beyond the schema; baseline 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 names a specific verb and resource ('List series') and scopes it to 'the Polymarket US exchange', which implicitly separates it from the sibling polymarket_series_list. It does not explicitly name or contrast the sibling, so the differentiation is inferential rather than stated.

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 tool versus polymarket_series_list, polymarket_us_events_list, or polymarket_series_get. Nothing states prerequisites, when-not-to-use, or how to choose the US variant over the global one.

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